B
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.TimeSpan' is defined in multiple places; using
definition from c:\WINDOWS\Microsoft.NET\Framework
\v1.1.4322\mscorlib.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.cab
2) c:\windows\servicepackfiles\i386
3) c:\windows\Microsoft.Net\framework\v.1.1.4322
4) c:\windows\Microsoft.Net\framework\v.2.0.50717
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
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.TimeSpan' is defined in multiple places; using
definition from c:\WINDOWS\Microsoft.NET\Framework
\v1.1.4322\mscorlib.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.cab
2) c:\windows\servicepackfiles\i386
3) c:\windows\Microsoft.Net\framework\v.1.1.4322
4) c:\windows\Microsoft.Net\framework\v.2.0.50717
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