Browse by Tags
All Tags » IDE » Tools (RSS)
Sorry, but there are no more tags available to filter with.
-
|
SharpDevelop are other options and there are also converters that are commercially available. Contributed from George Shepherd's Windows Forms FAQ
|
-
|
There are some C# to VB.NET converters available. I've yet to see one that delivers 100% fidelity on the conversion, they are often adequate for most jobs. Here are two: both of them have discussions on their limitations and assumptions. Clarity Consulting...
|
-
|
See Resourcer for .NET by Lutz Roeder. Contributed from George Shepherd's Windows Forms FAQ
|
-
|
Sharpcvslib on SourceForge is a client CVS library written in C# for the .NET platform. Contributed from George Shepherd's Windows Forms FAQ
|
-
|
Check out NAnt , a free build tool that can be used to automate builds for .NET applications. Contributed from George Shepherd's Windows Forms FAQ
|
-
|
There are a number of them. NUnit is a system that we like. It uses .NET debugging support seamlessly and is painless to use. You have no excuse not to write unit tests anymore! Contributed from George Shepherd's Windows Forms FAQ , Visual Studio...
|
-
|
There are several commercial products that support this. Take a look at Metamill . Contributed from George Shepherd's Windows Forms FAQ
|
-
|
When the system fails to locate an assembly, it generates a log file. The Assembly Binding Log Viewer (Fuslogvw.exe) is a viewer program you can run from the command line that gives you access to this log. This log information helps you diagnose why the...
|
-
|
Launch Visual Studio .NET 2003. Select Tools | External Tools | Add . Add the settings show below: Title: ILDASM (or anything else of your choice) Command: C:\Program Files\Microsoft.NET\SDK\v1.1\Bin\ildasm.exe Arguments: $(TargetPath) Initial Directory...
|
-
|
You can create an assembly (DLL or EXE) from the IL file using the ILASM (ilasm.exe) utility. This utility is usually installed in the directory C:\WINNT\Microsoft.NET\Framework\v1.0.3705 (or the appropriate version number). If you want to run this utility...
|
-
|
You can covert a .NET assembly (DLL or EXE) into its IL using the ILDASM (ildasm.exe) utility. This is usually installed in: C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\Bin. If you want to run this utility via command line, it would help...
|
-
|
The best one that I know of is Reflector for .NET by Lutz Roeder. You can also use the Windows Class Viewer (wincv.exe) and ILDASM (ildasm.exe), both of which come with the .NET Framework. Contributed from George Shepherd's Windows Forms FAQ
|