After upgrade to 2.0, Error CS1595 System.TimeSpan is defined inmultiple places

[brentbackup]

I know I'm some years behind, but I just have the go-ahead to start
developing on .Net 2.0. While the development process goes ahead, I'm
to maintain the .Net 1.1 stuff on the same machine.

I downloaded and installed the 2.0 framework. As I understand it, 1.1
and 2.0 are supposed to play nice with each other. However, now when I
go about compiling a class using CSC.exe, I get this error (among
others):

---------------------
warning CS1595: 'System.TimeSpa n' is defined in multiple places; using
definition from c:\WINDOWS\Micr osoft.NET\Frame work
\v1.1.4322\msco rlib.dll
---------------------

Despite "only" being a warning, the compilation doesn't seem to take,
such that the DLL is not produced.

I've done an exhaustive search on the machine for multiple
mscorlib.dll files. There are four, in these locations:

1) c:\I386\netfx.c ab
2) c:\windows\serv icepackfiles\i3 86
3) c:\windows\Micr osoft.Net\frame work\v.1.1.4322
4) c:\windows\Micr osoft.Net\frame work\v.2.0.5071 7

If necessary, I will uninstall 2.0. That will probably fix it. Short
of that, however, is there any other solution?

Thanks for any pointers.

--Brent

[Marc Gravell]

Are you intentionally referencing both 1.1 and 2.0? What csc command
are you using? Call me lazy, but I do like using tools like VS, which
will sort out this type of issue for us...

Marc

[Brent]

On May 10, 1:53 pm, Marc Gravell <marc.grav...@g mail.comwrote:

Are you intentionally referencing both 1.1 and 2.0? What csc command
are you using? Call me lazy, but I do like using tools like VS, which
will sort out this type of issue for us...

Marc

Thanks for the heads up, Marc. My CSC command looks like this (sans
line feeds):

C:\[PathToCSC]\csc.exe
/t:library
/out:C:\[PathToBin]\bin\toolbox.dl l
C:\[PathToCSFile]\toolbox.cs
/r:c:\windows\Mi crosoft.NET\Fra mework\v1.1.432 2\System.Web.dl l
/r:c:\windows\Mi crosoft.NET\Fra mework\v1.1.432 2\mscorlib.dll
/r:c:\windows\Mi crosoft.NET\Fra mework\v1.1.432 2\System.Data.d ll
/r:c:\windows\Mi crosoft.NET\Fra mework\v1.1.432 2\system.dll
/r:c:\windows\Mi crosoft.NET\Fra mework\v1.1.432 2\system.web.dl l
/r:c:\windows\Mi crosoft.NET\Fra mework\v1.1.432 2\system.xml.dl l

Weird stuff...

[Marc Gravell]

And just checking: are you using the 1.1 version of csc, or the 2.0
one?

Marc

[Brent]

On May 11, 12:49 am, Marc Gravell <marc.grav...@g mail.comwrote:

And just checking: are you using the 1.1 version of csc, or the 2.0
one?

Marc

This is a good question. Actually, I'm using a csc.exe located in the
same folder as the .CS file. When I pointed to the CSC.exe file
located in c:\windows\Micr osoft.NET\Frame work\v1.1.4322\ , the
compiling works fine! Could it be that the absence of a csc.exe.config
in the local folder causes the csc to look all over the place for the
referenced namespaces, and come up with conflicts?

Whatever the case, I'm back on track.

Thanks, Marc.

--Brent

[Pavel Minaev]

On May 11, 9:28*pm, Brent <writebr...@gma il.comwrote:

This is a good question. Actually, I'm using a csc.exe located in the
same folder as the .CS file. When I pointed to the CSC.exe file
located in c:\windows\Micr osoft.NET\Frame work\v1.1.4322\ , the
compiling works fine! Could it be that the absence of a csc.exe.config
in the local folder causes the csc to look all over the place for the
referenced namespaces, and come up with conflicts?

Not really. It's just that csc always references some assemblies (in
particular, mscorlib) from the corresponding version of .NET
Framework, and then also those that you explicitly specify. In your
case, it would seem that this results in both mscorlib from 1.1 and
mscorlib from 2.0 being referenced, hence the clash.

.NET 1.1 and 2.0 do play nice with each other in a sense that they can
be installed side by side, and programs will run using whatever
version of .NET they were built with. But if you're compiling with csc
2.0, you should really be referencing 2.0 assemblies, not 1.1 ones.