Sign in to follow this  

[.net] VB.NET Standard doesn't support DLL assembly creation?

This topic is 4909 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I got the VB.NET standard that MS was giving away as part of their VB At the Movies promotion. Anyway, I can't find any option to create a DLL assembly. Am I just missing something, or does it really not support them?

Share this post


Link to post
Share on other sites
Hi Promit,

When you start a new Project, simply choose Class Library from the Wizard.

This is not a standard DLL though, but you can use it from VB6 by using Regasm <nameof.dll> and calling it like a standard ActiveX component.

Share this post


Link to post
Share on other sites
Well, yes, I know that.

The point is there isn't a class library option. So is there no other way to make a DLL?

Share this post


Link to post
Share on other sites
(In a combo box:)

Output Options:
Windows Application
Console Application


Am I to assume that it won't create a DLL, then?

Share this post


Link to post
Share on other sites
Guess not! However, you can use an executable the same way you can a DLL :P

Share this post


Link to post
Share on other sites
So there'd be nothing wrong with taking my own application, exposing it as a reference to a ICodeProvider, compiling some code, and letting it instantiate classes declared in my EXE?

Share this post


Link to post
Share on other sites
If you want a proper DLL you can always use the command line compiler, but sticking the exe project in VS standard would be the easiest for development.

Share this post


Link to post
Share on other sites
It does support them, but it just hides the option. The way I do it is,

1. Create a Windows Application projet, save it, and close VB.NET.
2. Open the .vbproj file in Notepad.
3. Under <Build><Settings>OutputType, replace WinExe with Library.
4. Save it and reopen it with VB.NET

I figured this out when I upgraded a VB.NET 2002 Professional project to VB.NET 2003 Standard.

Share this post


Link to post
Share on other sites

This topic is 4909 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this