Prev: How to get crash dump when a unhandled CException is thrown by a MFC app
Next: Set width of an Cedit control based on required characters
From: Raj on 6 Jan 2010 00:51
We have installed VS.NET 1.1 after instalation of VS.NET 2.0. Whenever
I create a project either in any version of VS, the solution file does
not reflect the version number of peoject.
Lets say I have created a project "webapplication1" in 2005 version.
So in the TraceListesner folder I have webapplication1.sln file, which
actually loks like its a .net 1.1 file.

check here the samples:

http://www.juliobattisti.com.br/tutoriais/herbertgois/certificacaocomcsharpdotnet008_clip_image002.jpg
From: Tom Serface on 6 Jan 2010 13:22
You should be able to change the version of .NET that is used in the
Assembly information properties. I think it is stored in the project file.

Tom

"Raj" <raj.kg13(a)gmail.com> wrote in message
news:07ed536f-ec06-405c-9007-bf2e33bc1c95(a)d20g2000yqh.googlegroups.com...
> We have installed VS.NET 1.1 after instalation of VS.NET 2.0. Whenever
> I create a project either in any version of VS, the solution file does
> not reflect the version number of peoject.
> Lets say I have created a project "webapplication1" in 2005 version.
> So in the TraceListesner folder I have webapplication1.sln file, which
> actually loks like its a .net 1.1 file.
>
> check here the samples:
>
> http://www.juliobattisti.com.br/tutoriais/herbertgois/certificacaocomcsharpdotnet008_clip_image002.jpg

 | 
Pages: 1
Prev: How to get crash dump when a unhandled CException is thrown by a MFC app
Next: Set width of an Cedit control based on required characters