| Author: Praveen 05 Jun 2004 | Member Level: Silver Points : 0 |
The article gives a nice intro to a very needy topic. However, English needs some improvement. Great article overall.
|
| Author: Rakesh Chander Sharma 02 Jul 2004 | Member Level: Silver Points : 0 |
Very nice article, english used is quite simple and thats the best part of it. A very nice article overall.
|
| Author: Ravi 17 Aug 2004 | Member Level: Bronze Points : 0 |
Its really very simple and great example
|
| Author: newmangl 08 Sep 2004 | Member Level: Bronze Points : 0 |
I don't believe you have to do any conversion to get an ActiveX/COM DLL to work in .NET, at least for non-GUI functionality, anyway. I recently created a VB ActiveX DLL that returned some string values, and it works just fine in an ASP.NET page. I simply added a COM reference to the VB DLL and used the VBProjectName.ClassName format to declare an instance of the object. Easy as pie, no conversion. We even create instances of Office in .NET, and Office is COM based also.
What am I missing?
|
| Author: Bert Credo 21 Dec 2004 | Member Level: Bronze Points : 0 |
Hi, I had the following activeX dll created in VB 6. DAL - Data Access Layer BLL - Business Logic Layer WFL - Work Flow Layer
which I used in ASP, it works fine. How can I apply these in C#? Im new on this environment. Where to put the ConnectionString in the Global.asax. Is in Application_Start or Session_Start?
In ASP, Global.asa I used to put in: Sub Session_OnStart Session("DOCTRACKER_CONNECTIONSTRING") = "Provider=SQLOLEDB;Server=servername;Database=databasename;UID=username;PWD=userpwd" End Sub
Please help how to apply in C#.
Thnks,
|
| Author: vijay 29 Apr 2005 | Member Level: Bronze Points : 0 |
good one for beginers... msg conveyed english doesn matter.... wateveh....
vijay
|
| Author: V.Venkatesa Prasath 19 Aug 2005 | Member Level: Bronze Points : 0 |
Thanks U. I will Except more such type of article Reg .NET From you.
Thanks, PrasathVV
|