The functions in the Microsoft.VisualBasic namespace are part of the base .NET install, so in a sense they are "pure" .NET functions.
There's no way not to reference the Microsoft.VisualBasic.DLL assembly in VB because the assembly is needed for language helpers as well as user functions. What you could do is remove the default import of the Microsoft.VisualBasic namespace which would make it more difficult to use functions from that namespace. Otherwise, though, there is no way to absolutely force people not to use the functions. Paul [MSFT] -----Original Message----- From: Yogesh Shetty [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 5:30 AM To: [EMAIL PROTECTED] Subject: VB6 Function Compatibility... Hi, VB.NET still supports some of the VB6 functions due to this there are some lazy programmers who are still using the VB6 function in VB.NET eg: Mid, Left, Right... when there is already equivalent function available in .NET are there any VB compiler level switch / or any other solution which will allow only pure .NET code thererby restricting the developer from entering any VB 6.0 compatible function... Alternative solution could be developing an IDE Add-in / Macro which will walk thru the code and check for the existence of the above function... Has anybody tried this out.. Regards Yogesh Shetty Team COE Financial Technologies (India) Ltd. URL: <http://www.ftindia.com> www.ftindia.com mailto : <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] contact : +91 22 6164145 You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
