"SAP Connector for .NET": Create Proxies Without Visual Studio 2003

NCo 3.0 differs significantly from NCo 2.0:

With .NET Connector 2.0, NCo design time will create a "proxy method" for each ABAP function module you want to call and for each specific class for each structure or table that this function module refers to. You had to create objects from these structure / table classes and pass them to the proxy method corresponding to the function module. Now with .NET Connector 3.0, the generated code no longer exists. Instead of one generated proxy method for each function module, there is one single IRfcFunction class whose Invoke () method dynamically executes each specified ABAP Function Module. And instead of a dedicated generated class for each structure and table, there is one common IRfcStructure class,representing all possible structures and likewise one common IRfcTable class for all tables. So basically instead of hard-wiring everything statically at design time, NCo 3.0 now handles everything dynamically at runtime. Another difference is that you no longer need to create objects for structures and tables yourself. You only create one IRfcFunction and it internally takes care of all the contained structures and tables (using lazy initialization).and it internally takes care of all the structures and tables it contains (using lazy initialization).and it internally takes care of all the structures and tables it contains (using lazy initialization).