There is no other workaround ?
If your solution contains a setup project and this setup project has been
built at least once, you get an Assembly Load error when you run the
Inheritance Picker in order to inherit from an existing form in your main
project.
This problem occurs because the setup project generates several executable
files - such as InstMsiA.exe, InstMsiW.exe, and Setup.exe - that aren't
valid .NET assemblies. However, the Inheritance Picker interprets these
files as assemblies and attempts to load them, which results in a failure.
The only solution to this problem is removing the setup project from the
solution, and re-add it to the solution only when you're about to package
the solution.
Daniel Pratt - 26 Aug 2003 14:02 GMT
Hi Bragadiru,
This was fixed in VS.Net 2003. You can upgrade for a measly $29 USD.
http://msdn.microsoft.com/vstudio/howtobuy/pricing.aspx
Regards,
Dan
> There is no other workaround ?
>
[quoted text clipped - 11 lines]
> solution, and re-add it to the solution only when you're about to package
> the solution.
Bragadiru - 26 Aug 2003 14:40 GMT
thanks.
it doesn't help me too much right now.
> Hi Bragadiru,
>
[quoted text clipped - 20 lines]
> > solution, and re-add it to the solution only when you're about to package
> > the solution.
Jeff Levinson - [mcsd] - 26 Aug 2003 15:04 GMT
In addition it's not necessary. The inheritance picker is
a nice little wizard that simply automates the following
process:
1. Add a new form to your project
2. Switch to code view
3. Change the "Inherits System.Windows.Forms.Form"
to "Inherits CustomForm"
That's all it automates - nothing else. Just don't use
the inheritance picker.
Jeff Levinson
Author of "Building Client/Server Applications with
VB.NET: An Example Driven Approach"
>-----Original Message-----
>thanks.
[quoted text clipped - 31 lines]
>
>.