Hi Yousif,

I'm not sure your issue came from ISNet.WinUI.HtmlEditor.dll. May I know what intersoft's control that you use ? And please let me know more detail about the issue.
The issue might be came from the other third party.

I'm currently works on environment: windows 7 OS, VS2010, and .NET 3.5 higher. And I never met the issue with ISNet.WinUI.HtmlEditor.dll. 
Is there something that you can show to me that an issue came from ISNet.WinUI.HtmlEditor.dll ?

Thank you.
Riendy

The issue comes up when you UPGRADE a 2008 project to 2010.  New projects don't seem to be affected.

After the project is upgraded, if the old project had .NET 1.1 assemblies, it causes issues with Microsoft's parsers in that they do NOT update the designer files correctly with the appropriate namespace on objects.

Microsoft said we can't have any .NET 1.1 assemblies in the 2008 project to upgrade to 2010.  So it's not specifically YOUR assembly that's the issue, it's the fact that it's a 1.1 assembly which is why I asked if you guys can provide it in a .NET 2.0 version at a minimum at this point.  Thank you.

[EDIT] I forgot to attach the included ISNet assemblies in our project.  Note that we do not include this assembly, but it still gets copied to the web app's Bin folder on compile.

Hi Yousif,

Sorry for the latest response. 
I assume this issue have a relation with your issue in other thread. If the issue in that page has solved and this issue still appear, We have to get more concern to this issue. So, I have colaborated with Yudi who handle your issue in that thread. We are trying to replicate your issue using vs2008 SP1 and unfortunately, we are unable to replicate that issue. 

would you please give us a permission to remote your desktop ? 

Regards.
Riendy 

No, this issue is NOT related, directly anyway, to the other one, however, we do need help on resolving the other issue Yudi is working on since we're still on VS2008.

I'd be happy to show you, via webex, if you'd like the other issue, however, I've already provided video and samples.

With this issue, it's going to require involving Microsoft as well.  Right now, unfortunately, I don't have the time to spend on this one.  It may be a few weeks until I'm free to devote time to this one, so e can touch base again at that time.

Essentially, when you update ASPX markup code, what happens is that the designer is not updated correctly with the control.  So, for example, if we add our own custom text box, say PrismVirtualTextBox from an assembly namespace called PRISM.VirtualInterface, the designer file woudl be incorrectly updated with the object from the wrong namespace, e.g., PRISM.BusinessLogic.PrismVirtualTextBox.

If you're attempting to duplicate, you'll have to create a solution with custom control classes and some "dummy" classes that are under the same top namespace in VS2008 first.  After you set up the test, you'll need to then upgrade your solution to VS2010 and then make updates to your ASPX code.  it may work for a while so you have to keep making updates until it breaks.  It may take several tries like it did with us.

Hi yousif,

Basically, to solve the issue, firstly we have to reproduce the issue here.
But, I have a trouble to reproduce your issue. 
Could you please give me your simple runable sample to riendy@intersoftpt.com. It is very help us to provide a solutions for your issue.

Regards.
Riendy

Hi Riendy,

It'll be difficult to provide a sample as this problem is not consistent.  But like I said in my initial email, it's not the problem with the assembly itself and it's not really an Intersoft problem.  Although that may not be a 100% certainty, but let us go with that premise for now.

There are two separate issues I see here:

1. Why is this WinUI assembly needed for web-based controls?  We don't use any WinForms and Windows UI components so we'd like to know why this is needed.  I'm assuming this is a WinForms assembly based on the naming.
2. Microsoft has identified the source being assemblies that are .NET 1.1.  With that being the case, can't you guys just provide a new version of this assembly compiled under, at minimum, the .NET Framework 2.0?  I know that 2.0 was a major upgrade over 1.1 so I can understand that it may require more than just a simple recompile, but now that .NET is up to version 4.0, it's probably time to get rid of any 1.1 assemblies to avoid future problems anyway don't you agree?

You can easily create your own VS2008 solution with some custom control projects (just create some dummy controls that derive from existing classes like TextBox, Label, etc.) and a web applicaton project (NOT web site) with several ASPX pages.  Then convert it to VS2010, then attempt to make updates to the aspx pages.  Right now I just don't have the time to create a sample for you as it's a bit time consuming.

Hi Yousif,

I need to consult about your issue to our developers before I can provide any solutions for you.
I'll be back to this thread with a solution for you as soon as possible.

Take your time Yousif.

Regards.
Riendy