Re: Creating a DLL
From: Richard Troxell (rtroxell_at_tampabay.rr.com)
Date: 03/01/05
- Previous message: Scott M.: "Re: Creating a DLL"
- In reply to: Scott M.: "Re: Creating a DLL"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Mar 2005 12:54:35 -0500
I appreciate your concern and I understand what you are saying about why it
shouldn't be done this way. The fact of the matter is that this is the way
I am being instructed to accomplish this task. VB 6.0 is not an option
either. .Net is all that I have available.
-- Richard Troxell "Scott M." <s-mar@nospam.nospam> wrote in message news:%23DAN%23PoHFHA.1500@TK2MSFTNGP09.phx.gbl... >I really don't think that this is something you would want to do. Here's >why: > > The MS Common Dialog Control is an ActiveX control (COM). Using it from > .NET means that you will be using COM InterOp and the ActiveX control will > need to have a Runtime Callable Wrapper placed around it. COM InterOp, by > its very nature, implies a performance hit. > > Assuming you do go down this road, now you want to take the .NET component > (which is wrapping the functionality of a COM component) and you want to > use this .NET component in a COM environment (VBScript). Now, you are > taking the COM object, which is wrapped up inside of a .NET object and > re-wrapping it again so that it looks like a COM object. You will need to > create a COM Callable Wrapper around the .NET component, which is wrapping > the COM component. > > Because you will be using COM InterOp, you will inherently be causing a > performance hit to be taken. But because of the unnecessary and excessive > use of it, you would really experience performance degradation. > > The specific nature of what you are trying to do here (allow users to > save/open/brows files and folders on a web server) is the definition of a > security nightmare scenario. > > I'm sorry I couldn't be more helpful, but there is nothing in your plan > that sounds like something you would ever want to do. > > If you are dead set on using the Common Dialog control, I would suggest > getting your hands on a copy of VB 6.0 and using it from there. At least > this way, you don't have to bring .NET into it at all and therefore remove > all the COM InterOp from the process. > > -Scott > > > "Richard Troxell" <rtroxell@tampabay.rr.com> wrote in message > news:us%231BXnHFHA.720@TK2MSFTNGP10.phx.gbl... >>I do understand the difference between ASP and ASP.NET. >> >> I am not using .NET to produce this solution. >> I am trying to create an object that encapsulates the Microsoft Common >> Dialog so that I can display a file open/save prompt to users of a >> existing HTML pages. The open/save will be used to process Office Web >> Component templates that are displayed on these pages. The HTML pages >> already exist and are already deployed through the use of shortcuts on >> user's desktops. The only tool that I have available to create the object >> is VB.NET. I can't simply reference the MS Common Dialog through the >> VBScript in the HTML pages because the dialog control is licensed and >> therefore not distributable for use in VBScript. By encapsulating the >> common dialog in a class created through a licensed development tool >> (VB.NET), I will then be able to reference the new object through the use >> of VBScript and HTML without violating any Microsoft licensing >> agreements. >> >> -- >> Richard Troxell >> >> "Scott M." <s-mar@nospam.nospam> wrote in message >> news:egvjwEiHFHA.3108@tk2msftngp13.phx.gbl... >>>I don't think you understood what I said. >>> >>> I am not advocating the use of ASP (and by ASP, I assume you are talking >>> about Classic ASP). I'm talking about ASP.NET (not the same thing as >>> ASP). If you are doing web page development in .NET, you are using >>> ASP.NET. >>> >>> You say you want an HTML web page that contains the file save/file open >>> dialog box. In .NET, that means you want to create an ASP.NET page that >>> uses these dialogs. >>> >>> You say the page is part of a solution that is "deployed through HTML" >>> so converting it to ASP is not an option. What exactly does that mean? >>> Are you building a web based application or not? If you are, then you >>> ARE using ASP.NET. >>> >>> Again, I'll say that you don't use the file open/file save dialog via >>> web pages as you wouldn't want users to be able to open and save files >>> to your web server (much less browse the folder structure of your web >>> server) in this way. >>> >>> If you could be clearer about what you are building and what the user >>> interface for it is (Windows Forms, Web Forms, Web Service, Component, >>> Windows Service, etc.) and what you need to accomplish, we could give >>> you some more specific advice. But, from what you've said so far, it >>> sounds to me like you don't quite understand (no insult intended here) >>> what web pages in .NET are all about and how they work. That's why I >>> gave you the links. >>> >>> >>> "Richard Troxell" <rtroxell@tampabay.rr.com> wrote in message >>> news:uuiWyfgHFHA.2924@TK2MSFTNGP15.phx.gbl... >>>> Thanks for the information. I am not building the page in ASP. I am >>>> using HTML to build the web page and need to display a file save/file >>>> load dialog box as part of the page. This page is part of a solution >>>> that we are deploying through HTML so converting to ASP is not an >>>> option at this point. What I need is information on how to create the >>>> DLL through VB.NET because those are the tools that I have available. >>>> >>>> Thanks again for the ASP links. I will research those for future >>>> projects but I am constrained to the tools mentioned above for this >>>> application. >>>> Any information on these tools would be appreciated. >>>> >>>> -- >>>> Richard Troxell >>>> >>>> "Scott M." <s-mar@nospam.nospam> wrote in message >>>> news:e%23jN2tdHFHA.2700@TK2MSFTNGP09.phx.gbl... >>>>> You do not register .NET .dll's. >>>>> >>>>> What you are trying to do doesn't make much sense in VB.NET. Instead >>>>> of VBScript, you would use VB.NET to create an ASP.NET web page. Web >>>>> pages don't use the Common Dialog Control because you wouldn't be >>>>> opening or saving files this way on a web server. >>>>> >>>>> I would suggest you learn more about what ASP.NET actually is and what >>>>> you can accomplish with it. Microsoft Press books are good. >>>>> http://asp.net, http://gotdotnet.com, http://msdn.microsoft.com are >>>>> all good resources. >>>>> >>>>> >>>>> >>>>> "Richard Troxell" <rtroxell@tampabay.rr.com> wrote in message >>>>> news:ukqVgWbHFHA.2852@TK2MSFTNGP12.phx.gbl... >>>>>>I am extremely new to VB .net and COM objects. I would like to create >>>>>>and register a DLL that contains the Microsoft Common Dialog box so >>>>>>that I can use that dll in a VBScript via Html. Can you please point >>>>>>me to a book or group or site that can provide detailed instructions >>>>>>on accomplishing this? >>>>>> >>>>>> Thank you. >>>>>> >>>>>> -- >>>>>> Richard Troxell >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
- Previous message: Scott M.: "Re: Creating a DLL"
- In reply to: Scott M.: "Re: Creating a DLL"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
