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 / Distributed Applications / August 2003

Tip: Looking for answers? Try searching our database.

Is this true ?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bragadiru - 26 Aug 2003 12:38 GMT
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]
>
>.

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.