.NET 2.0 And MSI 3.0 Incompatible

[Guest]

OS win2003 server
..NET 1.0 , 1.1 & 2.0 beta installed
VS studio 2003 installed
VS Studio 6.0 installed

When I don't had .NET 2.0 beta my MSI file was working fine.
Now After .NET 2.0 beta
I get errors for Assembly installation...Here are msi log info.


MSI (s) (D0:44): Executing op:
ComponentRegister(ComponentId={496B4EED-C4EC-4598-ACD7-3716ED898522},KeyPath=<\ABCDInterop,Version="1880.4.5.0",FileVersion="1880.4.5.0",GUID="bd3486d1-9a88-11d2-9431-00a0c95ab63b",PublicKeyToken="23106a86e706d0ae
",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (D0:44): Assembly Error:The given assembly name or codebase, '%1',
was invalid.
MSI (s) (D0:44): Note: 1: 1935 2: 3: 0x80131047 4: 5:
CreateAssemblyNameObject 6:
ABCDInterop,Version="1880.4.5.0",FileVersion="1880.4.5.0",GUID="bd3486d1-9a88-11d2-9431-00a0c95ab63b",PublicKeyToken="23106a86e706d0ae"
DEBUG: Error 2908: Could not register component
{496B4EED-C4EC-4598-ACD7-3716ED898522}.
MSI (c) (5C:24): Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell
Dlg, Ret=MS Shell Dlg



ABCDInterop.dll is interop dll. I can manually add to GAC & able to do
Regasm.

Any idea why MSI blow up...?????????????????????

 

[Guest]

Not sure why it is blowing up, but there is always a risk when you play with
beta software. I, personally, have set up Virtual PC for my .NET 2.0 work.


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************