Click here to Skip to main content
11,641,064 members (59,435 online)
Click here to Skip to main content

Compile VB.NET code without Microsoft.VisualBasic.dll

, 1 Aug 2006 CPOL 76K 19
Rate this:
Please Sign up or sign in to vote.
Compile VB.NET code without an implicit reference to Microsoft.VisualBasic.dll.

Introduction

Let's say you are developing a program using Visual Basic .NET (2003 or 2005), and you wish to make sure that your code is using "pure" .NET and is VB6 free.

Background

As you all know, Visual Basic .NET enables you to code using VB 6 legacy syntax and keywords. For example, we can use CInt, Mid, InStr etc. The implementation of the compatibility layer is at the Microsoft.VisualBasic.dll library.

Behind the scene

When compiling your program, using either the Visual Studio IDE or the vbc command line compiler, Microsoft.VisualBasic.dll is added as a reference, and there is no direct approach of removing this reference. The official (and quite not reasonable) solution to the problem is to add the -sdkpath command line option to the vbc (you cannot set this option in a VB Visual Studio project). Copy the .NET platform assemblies that are required by your project references, into a different directory, and build your program from the command line, having the -sdkpath pointing to that directory.

Behind the whole theater

There is an undocumented vbc command line option -novbruntimeref, which you can use (at your own risk Smile | :) , as an alternative to -sdkpath. Adding -novbruntimeref excludes the implicit addition of the Microsoft.VisualBasic.dll reference. For example, compiling with the -novbruntimeref option will fail if you will use Mid instead of Substring.

Now, your compilation is VB6 free. And don't get me wrong, VB was a great friend of mine since VB3, and some of my best friends are ... well, you got the point.

Should I stop using the Microsoft.VisualBasic namespace?

Yes and No.

No - Productivity. If you wish to parse strings using the VB6 Mid instead of Substring, it's your call. After all, this layer was made for enabling you to import VB6 applications into .NET, seamlessly, without code changes.

Yes - Compatibility. For example, VB6 collections are 0 based for read, and -1 based for insertion. Upgraded application that use VB collections through inconsistent implementations of IList may experience some bugs.

Both points are very important. The choice is all yours.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Rafael Mizrahi
Chief Technology Officer Feng-GUI
United States United States
Rafael Mizrahi is a CTO at Feng-GUI

He is also a hacker contributor at the mono project, and a GarageGeeks member.

Rafael Mizrahi personal blog -
http://rafaelmizrahi.blogspot.com

You may also be interested in...

Comments and Discussions

 
NewsMicrosoft now released this feature in VB9 ORCAS Pin
Rafael Mizrahi12-Jun-07 0:37
memberRafael Mizrahi12-Jun-07 0:37 
Questionwhat happen when I use DirListBox in c# Pin
Do.It11-Apr-07 1:00
memberDo.It11-Apr-07 1:00 
GeneralYou people need to calm down [modified] Pin
LuharVB25-Jan-07 7:01
memberLuharVB25-Jan-07 7:01 
AnswerRe: You people need to calm down Pin
Rafael Mizrahi25-Jan-07 7:26
memberRafael Mizrahi25-Jan-07 7:26 
Newsnovbruntimeref compiler option Pin
Rafael Mizrahi4-Aug-06 0:10
memberRafael Mizrahi4-Aug-06 0:10 
GeneralWrong reason Pin
jwelch23-Aug-06 4:42
memberjwelch23-Aug-06 4:42 
QuestionWhy? Pin
jwelch21-Aug-06 4:10
memberjwelch21-Aug-06 4:10 
GeneralRe: Why? Pin
Anthony Missico3-Aug-06 9:01
memberAnthony Missico3-Aug-06 9:01 
AnswerRe: Why? [modified] Pin
Michel Posseth1-Aug-06 22:51
memberMichel Posseth1-Aug-06 22:51 
General[Message Deleted] Pin
Rafael Mizrahi1-Aug-06 23:07
memberRafael Mizrahi1-Aug-06 23:07 
GeneralRe: Why? Pin
Michel Posseth1-Aug-06 23:36
memberMichel Posseth1-Aug-06 23:36 
GeneralRe: Why? [modified] Pin
Anthony Missico3-Aug-06 9:06
memberAnthony Missico3-Aug-06 9:06 
GeneralPrevent the reference being added to new projects ... Pin
Duncan Edwards Jones28-Jul-06 6:47
memberDuncan Edwards Jones28-Jul-06 6:47 
GeneralRe: Prevent the reference being added to new projects ... Pin
dfinger1-Aug-06 1:38
memberdfinger1-Aug-06 1:38 
GeneralRe: Prevent the reference being added to new projects ... Pin
Daniel Finger1-Aug-06 2:28
memberDaniel Finger1-Aug-06 2:28 
GeneralRe: Prevent the reference being added to new projects ... Pin
lpellerin6-Sep-06 3:37
memberlpellerin6-Sep-06 3:37 
Well you can easily remove it in VS2005 by going in your Project's properties, then clicking on the Reference section, and finally, unchecking "Microsoft.VisualBasic". A quick recompile will show all the "bad" stuff you have used thus far in your project.
GeneralRe: Prevent the reference being added to new projects ... Pin
Rafael Mizrahi6-Sep-06 21:04
memberRafael Mizrahi6-Sep-06 21:04 
QuestionRe: Prevent the reference being added to new projects ... Pin
nitkapy2k@gmail.com12-Mar-08 21:42
membernitkapy2k@gmail.com12-Mar-08 21:42 
GeneralRe: Prevent the reference being added to new projects ... Pin
Rafael Mizrahi12-Mar-08 22:01
memberRafael Mizrahi12-Mar-08 22:01 
GeneralRe: Prevent the reference being added to new projects ... Pin
nitkapy2k@gmail.com13-Mar-08 4:29
membernitkapy2k@gmail.com13-Mar-08 4:29 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.150731.1 | Last Updated 1 Aug 2006
Article Copyright 2006 by Rafael Mizrahi
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid