Print Page | Close Window

After upgrading to the latest HotFix from Infragistics 6.3, the Windows Designer did not function

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=295
Printed Date: 12-Jun-2026 at 1:26am


Topic: After upgrading to the latest HotFix from Infragistics 6.3, the Windows Designer did not function
Posted By: Customer
Subject: After upgrading to the latest HotFix from Infragistics 6.3, the Windows Designer did not function
Date Posted: 16-Jul-2007 at 2:49pm

After upgrading to the latest HotFix from Infragistics 6.3  the Windows Designer did not function in forms with Infragistics control.


Replies:
Posted By: IdeaBlade
Date Posted: 16-Jul-2007 at 2:50pm
I downloaded the HotFix, but could not duplicate the problem.  I have attached a sample VB solution.

Posted By: Customer
Date Posted: 16-Jul-2007 at 2:51pm
I want to thank you for sending that file to me because it helped in solving our issue.

If you want the story it's as follows (with most of the boring stuff cut out so it seems like i solved it in 10 minutes).

I received your file with the statement that it worked fine. Opened it up and went to the Form1 designer.. BOOM! same error as before. Sent it to my colleague, who had the same error. Then because I was curious tried to compile the program to see what it ran like. This ALSO gave me an error, which was not occuring when we ran our native solution.

Looking at this error it said it couldn't find Infragistics 6.3.1056 (which is a previous HOTFIX). So I re-ran the IdeaBlade Assembly Binding Redirector. When I tried to compile your solution the same error came up.

This made me curious to see what was in the Machine.config file, so I went and opened it up and noticed that there were two binding redirects. One for Hotfix 1056 and another for Hotfix 1059. I removed the redirect for 1056 and ran your file. It worked... went into our solution and looked at one of the designer forms, works like a charm.

So just to let you know if you come across this with another customer, one of the things to check is the machine.config file for the correct redirects.

Again thanks for your time and effort. Without your quickApp never would have figured it out.

Posted By: IdeaBlade
Date Posted: 16-Jul-2007 at 2:52pm

Great detective work!

This sounds like it may be a bug on our part.

Could you send me the previous HotFix so we can we can see whether we can come up with a fix for your environment? I'd rather you not have to manually edit the machine.config file.

Thanks in advance for your help in this matter.


Print Page | Close Window