Single source code to compile over .NET 1.0, 1.1, 2.0 and CF

V

Vipul Pathak

Hi everyone,

I have a .NET 1.1 application ready to be ported on .NET 2.0.

With some of the features made obsolete in 2.0 and the new recomended
methods are not available in .NET 1.1, It leaved me with a question in mind:

How come I conditionally compile my application with .NET 1.1 and 2.0 ?

An example of obsolete method in 2.0 is:
//-------------------------------------------------------------------
// .NET 1.1: OK, .NET 2.0: Warning, Property
ConfigurationSettings.AppSettings is obsolete !
string szNewKbAddr =
System.Configuration.ConfigurationSettings.AppSettings[AppConstant.KEY_NEW_K
B_ADDRESS];

// .NET 1.1: Error, .NET 2.0: OK
string szNewKbAddr =
System.Configuration.ConfigurationManager.AppSettings[AppConstant.KEY_NEW_KB
_ADDRESS];
//-------------------------------------------------------------------


I have used the code block similar to below, for conditional compilation of
code for .NET 1.1 and .NET CF:
//-------------------------------------------------------------------
#if(_WIN32_WCE)
... ... .NET CF specific code ... ...
#else
... ... .NET 1.1 specific code ... ...
#endif
//-------------------------------------------------------------------

Do we have any solution, to either conditionally compile the single source
code application on different versions of .NET ( 1.1 and 2.0 ) ?
OR- any other solution please ?

Thanks ...

* (Vipul)() ;
 
F

Frans Bouma [C# MVP]

Vipul said:
Hi everyone,

I have a .NET 1.1 application ready to be ported on .NET 2.0.

With some of the features made obsolete in 2.0 and the new recomended
methods are not available in .NET 1.1, It leaved me with a question
in mind:

How come I conditionally compile my application with .NET 1.1 and 2.0
?

An example of obsolete method in 2.0 is:
//-------------------------------------------------------------------
// .NET 1.1: OK, .NET 2.0: Warning, Property
ConfigurationSettings.AppSettings is obsolete !
string szNewKbAddr =
System.Configuration.ConfigurationSettings.AppSettings[AppConstant.KEY
_NEW_K B_ADDRESS];

// .NET 1.1: Error, .NET 2.0: OK
string szNewKbAddr =
System.Configuration.ConfigurationManager.AppSettings[AppConstant.KEY_
NEW_KB _ADDRESS];
//-------------------------------------------------------------------


I have used the code block similar to below, for conditional
compilation of code for .NET 1.1 and .NET CF:
//-------------------------------------------------------------------
#if(_WIN32_WCE)
... ... .NET CF specific code ... ...
#else
... ... .NET 1.1 specific code ... ...
#endif
//-------------------------------------------------------------------

Do we have any solution, to either conditionally compile the single
source code application on different versions of .NET ( 1.1 and 2.0 )
? OR- any other solution please ?

Thanks ...
Click to expand...

Create nmake files and pass a define, like NET20. In the source, you
place
#if NET20
//... .net 20 specific
#endif
#if NET11
//... .net 11 specific
#endif

statements.

Example: (makefile_20)
SOURCES=AssemblyInfoDotNet20.cs DynamicQueryEngine.cs
SqlServerSpecificCreator.cs

REFERENCES=SD.LLBLGen.Pro_ORMSupportClasses.NET20.dll
REFDIR=..\ORMSupportClasses\DotNET2.0\bin\

all : $(SOURCES)
csc /t:library
/out:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll
/doc:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.S
qlServer.NET20.xml /d:TRACE,DOTNET20 /o /lib:$(REFDIR) /r:$(REFERENCES)
$(SOURCES)

debug : $(SOURCES)
csc /t:library /debug
/out:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll
/d:TRACE,DEBUG,DOTNET20 /lib:$(R
EFDIR) /r:$(REFERENCES) $(SOURCES)

clean:
del /Q DotNET2.0\bin\SD.LLBLGen.Pro.DQE.SqlServer.NET20.*


and I start this with a simple .cmd file:
mkdir DotNET2.0\bin
nmake /nologo /f makefile_20 clean
nmake /nologo /f makefile_20

Frans



--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
V

Vipul Pathak

Thanks a lot ..... :)

* (Vipul)() ;


Frans Bouma said:
Vipul said:
Hi everyone,

I have a .NET 1.1 application ready to be ported on .NET 2.0.

With some of the features made obsolete in 2.0 and the new recomended
methods are not available in .NET 1.1, It leaved me with a question
in mind:

How come I conditionally compile my application with .NET 1.1 and 2.0
?

An example of obsolete method in 2.0 is:
//-------------------------------------------------------------------
// .NET 1.1: OK, .NET 2.0: Warning, Property
ConfigurationSettings.AppSettings is obsolete !
string szNewKbAddr =
System.Configuration.ConfigurationSettings.AppSettings[AppConstant.KEY
_NEW_K B_ADDRESS];

// .NET 1.1: Error, .NET 2.0: OK
string szNewKbAddr =
System.Configuration.ConfigurationManager.AppSettings[AppConstant.KEY_
NEW_KB _ADDRESS];
//-------------------------------------------------------------------


I have used the code block similar to below, for conditional
compilation of code for .NET 1.1 and .NET CF:
//-------------------------------------------------------------------
#if(_WIN32_WCE)
... ... .NET CF specific code ... ...
#else
... ... .NET 1.1 specific code ... ...
#endif
//-------------------------------------------------------------------

Do we have any solution, to either conditionally compile the single
source code application on different versions of .NET ( 1.1 and 2.0 )
? OR- any other solution please ?

Thanks ...
Click to expand...

Create nmake files and pass a define, like NET20. In the source, you
place
#if NET20
//... .net 20 specific
#endif
#if NET11
//... .net 11 specific
#endif

statements.

Example: (makefile_20)
SOURCES=AssemblyInfoDotNet20.cs DynamicQueryEngine.cs
SqlServerSpecificCreator.cs

REFERENCES=SD.LLBLGen.Pro_ORMSupportClasses.NET20.dll
REFDIR=..\ORMSupportClasses\DotNET2.0\bin\

all : $(SOURCES)
csc /t:library
/out:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll
/doc:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.S
qlServer.NET20.xml /d:TRACE,DOTNET20 /o /lib:$(REFDIR) /r:$(REFERENCES)
$(SOURCES)

debug : $(SOURCES)
csc /t:library /debug
/out:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll
/d:TRACE,DEBUG,DOTNET20 /lib:$(R
EFDIR) /r:$(REFERENCES) $(SOURCES)

clean:
del /Q DotNET2.0\bin\SD.LLBLGen.Pro.DQE.SqlServer.NET20.*


and I start this with a simple .cmd file:
mkdir DotNET2.0\bin
nmake /nologo /f makefile_20 clean
nmake /nologo /f makefile_20

Frans



--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
Click to expand...
 
N

Nick Hounsome

Vipul Pathak said:
Hi everyone,

I have a .NET 1.1 application ready to be ported on .NET 2.0.

With some of the features made obsolete in 2.0 and the new recomended
methods are not available in .NET 1.1, It leaved me with a question in
mind:

How come I conditionally compile my application with .NET 1.1 and 2.0 ?
Click to expand...

Obsolete doesn't mean that they wont work.

I would just use the obsolete methods and ignore the warnings - you are less
likely to get version specific bugs that way.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Code that compiles under both ASP.NET 1.1 and 2.0? 4
.NET framework 1.1 and 2.0 in one machine - How to make the web pages work for these versions ??? 4
from .NET 1.0 to .NET 1.1 3
PostBack Events on Server Running .NET 1.1 and 2.0 5
It is an error to use a section registered as allowDefinition='MachineToApplication' 1
[ANN] JRuby 1.1 RC 1 Released 20
Windows Authentication and web services with WSE 2.0 1
Musatov's 'Mode/Code' Primary method call 4

Members online

Total: 35 (members: 1, guests: 34)
Robots: 521

Forum statistics

Threads
473,769
Messages
2,569,579
Members
45,053
Latest member
BrodieSola

Latest Threads

Top