Compiling VS2005 project for .NET framework 1.0 or 1.1

[Dave Booker]

I need to compile a VS2005 project to run using the 1.1 framework (i.e.,
app.config containing <supportedRunti me version="v1.1.4 322" /> ).

(If I just compile and run with such a setting it functions, but I can't
tell which framework it's using.)

Is there any way to specifically compile for 1.1 with the standard Studio,
or do I have to seek recourse with plug-ins like the following?

http://www.gotdotnet.com/codegallery...a-9b8d00970371

[Jeffrey Tan[MSFT]]

Hi Dave,

Thanks for your feedback!

You may provide my email(je***@onl ine.microsoft.c om(remove "online.")) to
the support engineer, he may contact me for any information he needed.

Also, you may feel free to share any progress here. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.

[jrett]

I too have been wondering why the build targets are sooo difficult to choose.
It should be able to simply build a .NET 1.1 bin version of the .NET code,
as long as the code is .NET 1.1 compliant.
Similarly, MSBuild should be able to build C/C++ code, or just run a command
line application. The targets should not have to be "Built in" or Patched,
or whatever MSBee does.

--
Jaan
""Jeffrey Tan[MSFT]"" wrote:

Hi Dave,

Thanks for your feedback!

You may provide my email(je***@onl ine.microsoft.c om(remove "online.")) to
the support engineer, he may contact me for any information he needed.

Also, you may feel free to share any progress here. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.

[Dave Booker]

Seems like a major oversight.

But just to follow up: I had a support incident escalated all the way to the
VS Development team and the answer on this was there's no native way to
target prior frameworks; MSBee, kludgy though it is, is the best solution for
now.

"jrett" wrote:

I too have been wondering why the build targets are sooo difficult to choose.
It should be able to simply build a .NET 1.1 bin version of the .NET code,
as long as the code is .NET 1.1 compliant.
Similarly, MSBuild should be able to build C/C++ code, or just run a command
line application. The targets should not have to be "Built in" or Patched,
or whatever MSBee does.

--
Jaan

[jrett]

I understand what you are saying, and I'm just now getting my feet wet with
MSBee, which seems to work pretty well, but I just cant figure why they tied
the executing environment so tightly to the build task.

I mean, it shouldn't matter what language, or therefore what version of a
language a build tool was implemented in, it should do it's job regardless of
what language or platform it was implemented on.

In this case, its job is to build software, whether C#/C/C++ or whatever.
It should not matter what the target/task is.

I just don't get the tight coupling.
--
Jaan
"Dave Booker" wrote:

Seems like a major oversight.

But just to follow up: I had a support incident escalated all the way to the
VS Development team and the answer on this was there's no native way to
target prior frameworks; MSBee, kludgy though it is, is the best solution for
now.

"jrett" wrote:

I too have been wondering why the build targets are sooo difficult to choose.
It should be able to simply build a .NET 1.1 bin version of the .NET code,
as long as the code is .NET 1.1 compliant.
Similarly, MSBuild should be able to build C/C++ code, or just run a command
line application. The targets should not have to be "Built in" or Patched,
or whatever MSBee does.

--
Jaan