C#, COM, ASP and .NET... LOST
-
Just checking but... Previously I would write COM components in VB, insert them into MTS and call those components from ASP. The purpose was to avoid putting lots of code into ASP pages not to mention other benefits. My question is that if I wanted to do the same in .NET with C#, MTS, by compiling my C# into a dll and inserting it into MTS much the same way ( maybe putting a SOAP interface into my C#) Does this architecture still apply in .NET ? Am i on the right track ? I shouldn't have a problem with C# as I do know Java. I'm just trying to figure out if I'm on the right track or not at this point .. I must say at this point I'm a bit overwhelmed by all that .NET has to offer. Can anyone recommend a book for exactly these types of applications ??? Thanks in advance.. Dato. :-D
-
Just checking but... Previously I would write COM components in VB, insert them into MTS and call those components from ASP. The purpose was to avoid putting lots of code into ASP pages not to mention other benefits. My question is that if I wanted to do the same in .NET with C#, MTS, by compiling my C# into a dll and inserting it into MTS much the same way ( maybe putting a SOAP interface into my C#) Does this architecture still apply in .NET ? Am i on the right track ? I shouldn't have a problem with C# as I do know Java. I'm just trying to figure out if I'm on the right track or not at this point .. I must say at this point I'm a bit overwhelmed by all that .NET has to offer. Can anyone recommend a book for exactly these types of applications ??? Thanks in advance.. Dato. :-D
If you are using ASP.NET, the recommended way to structure your application is to let it use x-copy deployment (ie you should just be able to copy the files to a new server and it will work). With that said there are a couple different options available. Create a class library in C# that contains all of the code that would have been placed in MTS. Place this dll in the /bin directory of every application that needs it then it will be loaded when referenced by the ASP.NET pages. Create a separate web application that exposes your class library from above as a web-service, then use the webservice from your ASP.NET pages. I'm not sure but Professional ASP.NET programming might cover what you are looking for in both cases. A simple example of the first case is covered in the Beginning version of the book. James Sonork ID: 100.11138 - Hasaki "I left there in the morning with their God tucked underneath my arm their half-assed smiles and the book of rules. So I asked this God a question and by way of firm reply, He said - I'm not the kind you have to wind up on Sundays." "Wind Up" from Aqualung, Jethro Tull 1971