Can you force VS 2005 to compile a program to be compatible with
version 1.x of the .NET Framework?  HOW!?

Just wondering, why would you want to?

Thanks,

Seth Rowe


jtertin wrote:
Show quoteHide quote

jtertin wrote:
No. You'll need VS 2002/2003 in order to do this. You can install them
side-by-side if you wish without any interference between the two.

theoretically.

Show quoteHide quote

jeff wrote:
Assuming that comment is in reference to the side-by-side installation, it's
certainly not just theory. I've got VS2003 and 2005 installed together on
both machines I work on and have absolutely no problems with it whatsoever.

glad u have better luck than me...

Show quoteHide quote

jeff wrote:
What problems have you experienced?

I'm interested in know what issues you had.  I have VS2003 and VS2005
installed on the same machine and have had no problems activlely developing
and maintaining applications with both versions.  Maybe we can help.

Show quoteHide quote

I heard about http://www.codeplex.com/Wiki/View.aspx?ProjectName=MSBee that
should do that.

The default situation is that each version of VS.NET targets a particular
version of the .NET framework (VS 2005 creates 2.0 applications, VS2003
targets 1.1 and VS 2002 targets 1.0).


Also a 1.1 application could be able to run under 1.0. Support for running a
2.0 application under 1.1 was dropped because there are so much additions
that it would be likely anyway that a vast majority of 2.0 applications
would use 2.0 specific features and couldn't run in 1.1).

Hope this helps.
1160525015.445888.285***@m7g2000cwm.googlegroups.com...
Show quoteHide quote

You can not force VS2005 to compile your assembly using the framework v1.1. 
However, assuming that your assembly CAN run in .NET v1.1 (if compiled with
VS2003), then you can do this.

1.  Complie your code in VS2005
2.  In your app.config file, use the <supportedRuntime> tag to force your
app to run in .NET v1.1

<configuration>
   <startup>
      <supportedRuntime version="v1.1.4322"/>
      <supportedRuntime version="2.0.50727"/>
   </startup>
</configuration>

That will force your assembly to run under v1.1.  If that is not installed,
it will run under v2.0.  I've only tried this once or twice before, but it
should work.

Show quoteHide quote

You can not force VS2005 to compile your assembly using the framework v1.1. 
However, assuming that your assembly CAN run in .NET v1.1 (if compiled with
VS2003), then you can do this.

1.  Complie your code in VS2005
2.  In your app.config file, use the <supportedRuntime> tag to force your
app to run in .NET v1.1

<configuration>
   <startup>
      <supportedRuntime version="v1.1.4322"/>
      <supportedRuntime version="2.0.50727"/>
   </startup>
</configuration>

That will force your assembly to run under v1.1.  If that is not installed,
it will run under v2.0.  I've only tried this once or twice before, but it
should work.


Show quoteHide quote

You can not force VS2005 to compile your assembly using the framework v1.1. 
However, assuming that your assembly CAN run in .NET v1.1 (if compiled with
VS2003), then you can do this.

1.  Complie your code in VS2005
2.  In your app.config file, use the <supportedRuntime> tag to force your
app to run in .NET v1.1

<configuration>
   <startup>
      <supportedRuntime version="v1.1.4322"/>
      <supportedRuntime version="2.0.50727"/>
   </startup>
</configuration>

That will force your assembly to run under v1.1.  If that is not installed,
it will run under v2.0.  I've only tried this once or twice before, but it
should work.


Show quoteHide quote

You can not force VS2005 to compile your assembly using the framework v1.1. 
However, assuming that your assembly CAN run in .NET v1.1 (if compiled with
VS2003), then you can do this.

1.  Complie your code in VS2005
2.  In your app.config file, use the <supportedRuntime> tag to force your
app to run in .NET v1.1

<configuration>
   <startup>
      <supportedRuntime version="v1.1.4322"/>
      <supportedRuntime version="2.0.50727"/>
   </startup>
</configuration>

That will force your assembly to run under v1.1.  If that is not installed,
it will run under v2.0.  I've only tried this once or twice before, but it
should work.

Show quoteHide quote

How to open a .CSV file ?
Moving Forms
Search for Directories/files/Folders
vb with odbc
DataTable - Date Difference
"using statments"
slightly OT: VB user base
File handling in VB
How to reference Webform textbox controls in a for next loop
VB.net app to run in the background