Annoying problem with VS.NET 2003 (VC++)
-
May be this might be a feature. Lets say you have an implementation file svrconndlg.cpp with top lines:-
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"Everytime you add a function using the wizard or override a event handler the top few line become
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"
#include ".\SvrConnDlg.h"Notoce the last line added by wizard. It does it everytime you use the wizard. Anyone else annoyed by it? I switched to VS.NET 2003 because I had problems with VS.NET 2002 with the resource editor. Looks like I should have sticked with VC++ 6.0 .
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
-
May be this might be a feature. Lets say you have an implementation file svrconndlg.cpp with top lines:-
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"Everytime you add a function using the wizard or override a event handler the top few line become
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"
#include ".\SvrConnDlg.h"Notoce the last line added by wizard. It does it everytime you use the wizard. Anyone else annoyed by it? I switched to VS.NET 2003 because I had problems with VS.NET 2002 with the resource editor. Looks like I should have sticked with VC++ 6.0 .
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
What happens if you change
#include "SvrConnDlg.h"
to
#include ".\SvrConnDlg.h"
Does it keep doing it then?
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
What happens if you change
#include "SvrConnDlg.h"
to
#include ".\SvrConnDlg.h"
Does it keep doing it then?
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
It works but I don't want to do that because the former method gives me more flexibility for moving files later on.
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
-
It works but I don't want to do that because the former method gives me more flexibility for moving files later on.
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
That's fair enough. What about using a
#pragma(once)inside the header file so it doesn't matter if it's included twice (or whatever the equivalent is in VC.NET) It's just a hack, but if it works...Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
That's fair enough. What about using a
#pragma(once)inside the header file so it doesn't matter if it's included twice (or whatever the equivalent is in VC.NET) It's just a hack, but if it works...Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
"#pragma once" works in .NET. phpWebNotes is a page annotation system modelled after php.net. http://webnotes.sourceforge.net/demo.php[^]
-
That's fair enough. What about using a
#pragma(once)inside the header file so it doesn't matter if it's included twice (or whatever the equivalent is in VC.NET) It's just a hack, but if it works...Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
the #pragma doesn't solve the path problems that may arise... right? -- I am on fire. Do you need a light?
-
the #pragma doesn't solve the path problems that may arise... right? -- I am on fire. Do you need a light?
Jörgen Sigvardsson wrote: the #pragma doesn't solve the path problems that may arise... right? That's right, but I can't think of anything else at the moment :(
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
May be this might be a feature. Lets say you have an implementation file svrconndlg.cpp with top lines:-
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"Everytime you add a function using the wizard or override a event handler the top few line become
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"
#include ".\SvrConnDlg.h"Notoce the last line added by wizard. It does it everytime you use the wizard. Anyone else annoyed by it? I switched to VS.NET 2003 because I had problems with VS.NET 2002 with the resource editor. Looks like I should have sticked with VC++ 6.0 .
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
Hell yeah, that is annoying.
David Wulff
This thing called love, it cries in a cradle all night It swings, it jives, it shakes all over like a jelly fish I kinda like it. Crazy little thing called love - Queen
-
May be this might be a feature. Lets say you have an implementation file svrconndlg.cpp with top lines:-
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"Everytime you add a function using the wizard or override a event handler the top few line become
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"
#include ".\SvrConnDlg.h"Notoce the last line added by wizard. It does it everytime you use the wizard. Anyone else annoyed by it? I switched to VS.NET 2003 because I had problems with VS.NET 2002 with the resource editor. Looks like I should have sticked with VC++ 6.0 .
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
Mine is doing that as well, causes a compilation error and I have to pick through and find the include that it added for me "helpfully". Also it opens a window to the msdn site every time I resize the main splitter bar but apparently I'm the only one that gets that as I posted about that a while ago and no one else claimed theirs did that as well. Good to see I'm not crazy with at least one bug. Wonder if MS is going to fix that include bug. ------------
-
Mine is doing that as well, causes a compilation error and I have to pick through and find the include that it added for me "helpfully". Also it opens a window to the msdn site every time I resize the main splitter bar but apparently I'm the only one that gets that as I posted about that a while ago and no one else claimed theirs did that as well. Good to see I'm not crazy with at least one bug. Wonder if MS is going to fix that include bug. ------------
John Cardinal wrote: Also it opens a window to the msdn site every time I resize the main splitter bar :wtf::wtf: That's probably is the bug of the year
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
-
May be this might be a feature. Lets say you have an implementation file svrconndlg.cpp with top lines:-
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"Everytime you add a function using the wizard or override a event handler the top few line become
#include "stdafx.h"
#include "ImpCmnUI.h"
#include "SvrConnDlg.h"
#include ".\SvrConnDlg.h"Notoce the last line added by wizard. It does it everytime you use the wizard. Anyone else annoyed by it? I switched to VS.NET 2003 because I had problems with VS.NET 2002 with the resource editor. Looks like I should have sticked with VC++ 6.0 .
I don't choose the targets - they present themselves to me in an almost garish display of submission and sacrifice. It's my duty to react as I do. - John Simmons/Outlaw Programmer
Rama -- I looked into this and found out that it is a known bug that is scheduled to be fixed in the next release. Sorry I don't have better news than that... Nick Hodapp This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2003 Microsoft Corporation. All rights reserved.