M
Mark Oliver
Hi,
Does anyone know where I can find a VB.net to C# converter?
Thanks,
Mark
Does anyone know where I can find a VB.net to C# converter?
Thanks,
Mark
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Richard A Lowe
M
Mark Oliver
Thanks, but it is no go. I have several non-supported commands including
AddressOf, AddHandler, and RemoveHandler. When I try anyway I get.
Server Error in '/' Application.
----------------------------------------------------------------------------
----
Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Mark
AddressOf, AddHandler, and RemoveHandler. When I try anyway I get.
Server Error in '/' Application.
----------------------------------------------------------------------------
----
Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Mark
T
Tom Dacon
You just typed your newsgroup post with the best converter there is - your
fingers.
Tom Dacon
fingers.
Tom Dacon
O
Oren Novotny
It's a bit tacky and you'll lose the local variable names, but you could try
using one of the decompilers on your compiled assembly. Most of them allow
you to output the source code in C# in a file...
--Oren
using one of the decompilers on your compiled assembly. Most of them allow
you to output the source code in C# in a file...
--Oren
R
Richard A. Lowe
Well, it's not perfect - sounds like you'll have to convert event handlers
by hand.
You could also try Reflector http://www.aisto.com/roeder/dotnet/ which you
can use to decompile Assemblies (which were coded in VB.NET) to C#.
Richard
by hand.
You could also try Reflector http://www.aisto.com/roeder/dotnet/ which you
can use to decompile Assemblies (which were coded in VB.NET) to C#.
Richard
D
Daniel Billingsley
I've wondered about that... I wonder what kind of spaghetti you'd end up
with if you used the tools to do:
VB6 -tool-> VB.NET -> IL -decompile -> C#
with if you used the tools to do:
VB6 -tool-> VB.NET -> IL -decompile -> C#
A
Al Ponomarev
I've wondered about that... I wonder what kind of spaghetti you'd end up
with if you used the tools to do:
VB6 -tool-> VB.NET -> IL -decompile -> C#
You can use Spices.Net Decompiler. This tool allows you to convert
assemblies into 6 languages (IL, C#, VB.Net, MC++, J# and Delphi.Net)
Best regards,
Al, 9Rays.Net