View Single Post
  #3 (permalink)  
Old April 10th, 2005, 05:49 PM
planoie's Avatar
planoie planoie is offline
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,413
Thanks: 0
Thanked 16 Times in 16 Posts
Default

From what I've found, what you get with VS.NET is enough to do native .NET development. Once you start branching into more mirky waters you have to start using the tools in the SDK.

Some examples of these tools are the exes used to build wrappers for getting .NET to place nicely with COM. To make a COM library work in .NET you use the tlbimp.exe program that builds a wrapper that .NET can call to talk to the COM objects. To go the other way, you use the regasm.exe program to register a .NET assembly with COM so COM programs can call it. There are tools for de-compiling assemblies, creating and assigning strong names to assemblies and all sorts of other stuff you might need to do in the course of more real-world development. (Wouldn't it be oh-so-nice to just develop native .NET applications.)

-Peter
Reply With Quote