Directly there is nothing... however if you use Lutz Roeder's .NET Reflector (http://www.aisto.com/roeder/dotnet/) and Denis Bauer's Reflector.FileDisassembler plugin (http://www.denisbauer.com/NETTools/FileDisassembler.aspx) you end up with the source for an assembly. Throw in some Visual Studio to build a project out of it, make your modifications and hit build.
Sure it’s a little roundabout, however currently it is the easiest way that I am aware of.
If you do software protection, I’d suggest looking into Dotfuscator (http://www.preemptive.com/products/dotfuscator/) for obfuscating of your code and making it much harder to decompile, let alone understand. Another nice feature of higher versions of Dotfuscator is that they can alter your assembly in such a way that even if you do decompile it, the output will not be in a compliable state, so any person going such a route would have to spend even more time just making it build.
Decompile,modify and recompile?
Andreas Kyriacou
Chip Zero
Directly there is nothing... however if you use Lutz Roeder's .NET Reflector (http://www.aisto.com/roeder/dotnet/) and Denis Bauer's Reflector.FileDisassembler plugin (http://www.denisbauer.com/NETTools/FileDisassembler.aspx) you end up with the source for an assembly. Throw in some Visual Studio to build a project out of it, make your modifications and hit build.
Sure it’s a little roundabout, however currently it is the easiest way that I am aware of.
If you do software protection, I’d suggest looking into Dotfuscator (http://www.preemptive.com/products/dotfuscator/) for obfuscating of your code and making it much harder to decompile, let alone understand. Another nice feature of higher versions of Dotfuscator is that they can alter your assembly in such a way that even if you do decompile it, the output will not be in a compliable state, so any person going such a route would have to spend even more time just making it build.