Re: Extermely nasty bug with the way .NET handles references
From: Andrew Baker (webmaster_at_vbusers.com)
Date: 12/09/04
- Next message: Nicholas Paldino [.NET/C# MVP]: "Re: Self terminating windows service"
- Previous message: Gisle Vanem: "Re: GAC confusion"
- In reply to: Nick Malik: "Re: Extermely nasty bug with the way .NET handles references"
- Next in thread: Nick Malik: "Re: Extermely nasty bug with the way .NET handles references"
- Reply: Nick Malik: "Re: Extermely nasty bug with the way .NET handles references"
- Messages sorted by: [ date ] [ thread ]
Date: 9 Dec 2004 09:21:30 -0800
I think you have misunderstood my post. I am not running the app, I am
using Visual Studio to design an application using a solution that
contains multiple projects. Several of the project reference each other
and the Form designer is having serious problems with this. It seems to
steam from the fact that I am using visual inheritance and the
inherited base components are in the same project as the components
that are deriving from them. This couple with the other information in
the previous post gives me a big headache!
I have used the Assembly Binding Log Viewer to look for the binding
errors, plus checked the temporary files in ..\Application
Data\Microsoft\VisualStudio\7.1\ProjectAssemblies are correct and still
haven't got to the bottom of this...
This is going to take someone with a serious knowledge of .NET to
solve. Have been using a million tools to watch what is going on, but
it seems so random!!!
- Next message: Nicholas Paldino [.NET/C# MVP]: "Re: Self terminating windows service"
- Previous message: Gisle Vanem: "Re: GAC confusion"
- In reply to: Nick Malik: "Re: Extermely nasty bug with the way .NET handles references"
- Next in thread: Nick Malik: "Re: Extermely nasty bug with the way .NET handles references"
- Reply: Nick Malik: "Re: Extermely nasty bug with the way .NET handles references"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|