Doing projects with Framework v1.0 in VS 2003?

[Niklas]

Hi
I have Visual Studio 2003 but I want to do a VB .NET project with Framework 1.0.3705. Is this possible?
I created a Hallo world application and changed the Reference Path to C:\WINNT\Microsoft.NET\Framework\v1.0.3705. All references changed to v 1.0 from v 1.1. When I tried to compile i got this error for a button: "Value of type 'System.Drawing.Point' cannot be converted to 'System.Drawing.Point'." Am I going to have a lot more problems if I create a bigger application?
Regards
/Niklas

[Niki Estner]

VS 2003 has a "what-framework-to-use" switch, hidden in the Project -
Properties - Common Properties - Build section. I must admit I never used
it, but I always assumed it does what you want to have without much ado...
Did you try that?

Niki

"Niklas" <Ni****@discussions.microsoft.com> wrote in
news:84**********************************@microsof t.com...

Hi
I have Visual Studio 2003 but I want to do a VB .NET project with Framework 1.0.3705. Is this possible? I created a Hallo world application and changed the Reference Path to C:\WINNT\Microsoft.NET\Framework\v1.0.3705. All references changed to v 1.0
from v 1.1. When I tried to compile i got this error for a button: "Value of
type 'System.Drawing.Point' cannot be converted to 'System.Drawing.Point'."
Am I going to have a lot more problems if I create a bigger application? Regards
/Niklas

[Herfried K. Wagner [MVP]]

* "Niki Estner" <ni*********@cube.net> scripsit:

VS 2003 has a "what-framework-to-use" switch, hidden in the Project -
Properties - Common Properties - Build section. I must admit I never used
it, but I always assumed it does what you want to have without much ado...
Did you try that?

.... but this will still create .NET 1.1 assemblies.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Niki Estner]

Really? I always assumed building a project with the "support only 1.0
framework" switch, the resulting executables would run fine on a
1.0-framework, and would behave the same if both framework versions are
installed side-by-side (i.e. use the 1.0 version). Is this wrong? If so,
what's that switch good for?

Niki

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in
news:2k************@uni-berlin.de...

* "Niki Estner" <ni*********@cube.net> scripsit:

VS 2003 has a "what-framework-to-use" switch, hidden in the Project -
Properties - Common Properties - Build section. I must admit I never used it, but I always assumed it does what you want to have without much ado... Did you try that?

... but this will still create .NET 1.1 assemblies.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Herfried K. Wagner [MVP]]

* "Niki Estner" <ni*********@cube.net> scripsit:

Really? I always assumed building a project with the "support only 1.0
framework" switch, the resulting executables would run fine on a
1.0-framework, and would behave the same if both framework versions are
installed side-by-side (i.e. use the 1.0 version). Is this wrong? If so,
what's that switch good for?

MSDN:

"
Microsoft .NET Framework v1.0 (advanced)
Specifies that the application will run only if version 1.0 of the
common language runtime is present on the computer.

Note When you specify version 1.0, the app.config file will be
modified with a section specifying that it can run on version 1.0 of the
runtime. The application will actually be built using the version 1.1
compiler, and will be a version 1.1 application in all other respects.
"

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Niki Estner]

So, if I got that right, the app will run on the 1.0 framework if compiled
with that switch. I thought that's what the OP wanted? At least, changing
the references (as he described it) should do about the same in my mind.

Niki

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in
news:2k************@uni-berlin.de...

* "Niki Estner" <ni*********@cube.net> scripsit:

Really? I always assumed building a project with the "support only 1.0
framework" switch, the resulting executables would run fine on a
1.0-framework, and would behave the same if both framework versions are
installed side-by-side (i.e. use the 1.0 version). Is this wrong? If so,
what's that switch good for?

MSDN:

"
Microsoft .NET Framework v1.0 (advanced)
Specifies that the application will run only if version 1.0 of the
common language runtime is present on the computer.

Note When you specify version 1.0, the app.config file will be
modified with a section specifying that it can run on version 1.0 of the
runtime. The application will actually be built using the version 1.1
compiler, and will be a version 1.1 application in all other respects.
"

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Herfried K. Wagner [MVP]]

* "Niki Estner" <ni*********@cube.net> scripsit:

So, if I got that right, the app will run on the 1.0 framework if compiled
with that switch. I thought that's what the OP wanted? At least, changing
the references (as he described it) should do about the same in my mind.

Yep, but as I said, it's still a .NET 1.1 application.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Niklas]

Using that switch helped me a lot, but with the information I have got from this thread, maybe I will develop my application with VS 2002.
Regards
/Niklas

"Niki Estner" wrote:

So, if I got that right, the app will run on the 1.0 framework if compiled
with that switch. I thought that's what the OP wanted? At least, changing
the references (as he described it) should do about the same in my mind.

Niki

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in
news:2k************@uni-berlin.de...

* "Niki Estner" <ni*********@cube.net> scripsit:

Really? I always assumed building a project with the "support only 1.0
framework" switch, the resulting executables would run fine on a
1.0-framework, and would behave the same if both framework versions are
installed side-by-side (i.e. use the 1.0 version). Is this wrong? If so,
what's that switch good for?

MSDN:

"
Microsoft .NET Framework v1.0 (advanced)
Specifies that the application will run only if version 1.0 of the
common language runtime is present on the computer.

Note When you specify version 1.0, the app.config file will be
modified with a section specifying that it can run on version 1.0 of the
runtime. The application will actually be built using the version 1.1
compiler, and will be a version 1.1 application in all other respects.
"

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Jay B. Harlow [MVP - Outlook]]

Niklas,
In addition to the other comments.

For details of side by side & having an assembly run under a different
version of the framework see:
http://msdn.microsoft.com/library/de...dexsidenet.asp

If you have VS.NET 2002, you can install both at the same time, and do the
new project in VS.NET 2002...

Hope this helps
Jay

"Niklas" <Ni****@discussions.microsoft.com> wrote in message
news:84**********************************@microsof t.com...

Hi
I have Visual Studio 2003 but I want to do a VB .NET project with Framework 1.0.3705. Is this possible? I created a Hallo world application and changed the Reference Path to C:\WINNT\Microsoft.NET\Framework\v1.0.3705. All references changed to v 1.0
from v 1.1. When I tried to compile i got this error for a button: "Value of
type 'System.Drawing.Point' cannot be converted to 'System.Drawing.Point'."
Am I going to have a lot more problems if I create a bigger application? Regards
/Niklas

[Niki Estner]

Just curious: Could you tell me what that means? Of course, the compiler is
v1.1, but the generated IL/Metadata should be 1.0-compatible. Also, the
application should use the 1.0-framework dll's, wouldn't it? I really
haven't ever worked with it, but you do seem to know something about it.

Niki

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in
news:2k************@uni-berlin.de...

* "Niki Estner" <ni*********@cube.net> scripsit:

So, if I got that right, the app will run on the 1.0 framework if compiled with that switch. I thought that's what the OP wanted? At least, changing the references (as he described it) should do about the same in my mind.

Yep, but as I said, it's still a .NET 1.1 application.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Jay B. Harlow [MVP - Outlook]]

Niki,

Of course, the compiler is
v1.1, but the generated IL/Metadata should be 1.0-compatible. 1.1 assemblies (.exe or .dll) are 1.0 compatible, however a 1.1 assembly
specifically references the 1.1 runtime, the 1.1 framework dlls.

Also, the
application should use the 1.0-framework dll's, wouldn't it? What the option does is add entries to the app.config file informing the
runtime to use the 1.0 framework dlls, instead of the 1.1 framework dlls.
Which means you need to be certain to include the app.config file when you
deploy your app.

Just curious: Could you tell me what that means? This article I previously posted explains it:
http://msdn.microsoft.com/library/de...dexsidenet.asp
Hope this helps
Jay

"Niki Estner" <ni*********@cube.net> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... Just curious: Could you tell me what that means? Of course, the compiler is v1.1, but the generated IL/Metadata should be 1.0-compatible. Also, the
application should use the 1.0-framework dll's, wouldn't it? I really
haven't ever worked with it, but you do seem to know something about it.

Niki

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in
news:2k************@uni-berlin.de...

* "Niki Estner" <ni*********@cube.net> scripsit:

So, if I got that right, the app will run on the 1.0 framework if compiled with that switch. I thought that's what the OP wanted? At least, changing the references (as he described it) should do about the same in my

mind.
Yep, but as I said, it's still a .NET 1.1 application.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>