Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / .NET SDK / January 2005

Tip: Looking for answers? Try searching our database.

Major bug in .NET loading 1.1 vs. 2.0

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David Thielen - 20 Jan 2005 16:57 GMT
Hi;

I have written a Word Add-In in C# that uses .NET 1.1. It all runs fine if
just .NET 1.1 is on a system. However, if .NET 2.0 is also installed, then
while the C# part runs fine, it cannot call vjslib 1.0.5000.0 (used for
zip/unzip) - it cannot find the file specified.

I log all assembly loadings, resolution failures, and exceptions. It is
loading .NET 1.1 and trying to load vjslib 1.0 in both cases. And the only
difference is installing/uninstalling the .NET 2.0 runtime.

The problem under 2.0 goes away if I create a windword.exe.config and set
the supportedRuntime version="v1.1.4322". However this solution won't work in
the case of a Word Add-In. Why? Well, what if another Add-In on install needs
a different config file? Then it overwrites mine and my Add-In is broken. Or
I install second and break the Add-In that installed first.

And the really strange thing is, in the case of no config file and .NET 2.0
installed, my Add-In is still started with .NET 1.1. It still wants to load
vjslib 1.0. The problem is it can't find vjslib 1.0.

It seems to me this is a bug - and a pretty serious one at that. Is there
any workaround other than Add-Ins tromping on each other's config file?

Signature

thanks - dave

"Peter Huang" [MSFT] - 21 Jan 2005 02:27 GMT
Hi

I reviewed the thread and find that there is a similar issue in the
newsgroup below.Now I have replied to you, you may go and take a look.
Subject: Installing .NET 2.0 causes exception in .NET 1.1 code
Newsgroups: microsoft.public.dotnet.framework.sdk

Best regards,

Perter Huang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.