create vb dll for non dotnet apps

[gg]

My standard version of dotnet 2003 basic does Not
have vbc.exe
have class library template
produce dll when outputtype is changed to classlib for .vbproj

it seems that standard version is not designed to build components
although the professional version is according to
http://www.greymatter.com/Buyers/dotnet/guide.asp

Is that correct? does that apply to MFC based DLL I want to make available
to non DotNet and non ms apps?

 

[Cor Ligthert]

GG,

VBC is AFAIK in every Net SDK, free for everybody.

I hope this helps,

Cor

 

[Ken Tucker [MVP]]

Hi,

http://www.devcity.net/Articles/111/1/vbnet_se_dll.aspx

Ken
-------------------
My standard version of dotnet 2003 basic does Not
have vbc.exe
have class library template
produce dll when outputtype is changed to classlib for .vbproj

it seems that standard version is not designed to build components
although the professional version is according to
http://www.greymatter.com/Buyers/dotnet/guide.asp

Is that correct? does that apply to MFC based DLL I want to make available
to non DotNet and non ms apps?

 

[Herfried K. Wagner [MVP]]

My standard version of dotnet 2003 basic does Not
have vbc.exe
have class library template
produce dll when outputtype is changed to classlib for .vbproj

it seems that standard version is not designed to build components
although the professional version is according to
http://www.greymatter.com/Buyers/dotnet/guide.asp

Normally changing the output type solves the problem. What happens if you
change the output type?

Creating class libraries with the Standard edition of Visual Basic .NET

Is that correct? does that apply to MFC based DLL I want to make
available to non DotNet and non ms apps?

The Standard edition of VB.NET cannot be used to build MFC DLLs. Not even
the Professional edition is able to to that.