Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Loading an .APP file from a VFP COM object
Message
From
05/05/2011 11:57:24
Scott Malinowski
Arizona Fox Software LLC
Arizona, United States
 
 
To
05/05/2011 11:48:33
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Miscellaneous
Thread ID:
01503828
Message ID:
01509665
Views:
50
Likes (1)
>Again, are you trying to load the component into Visual Studio at design time? I think that's not what you want, but you're making a common mistake by people coming from Visual FoxPro.

No, I am not creating anything in VS. I'm just doing the VFP side of things. The VS development is an outside firm. They need a VFP COM object from me so they can sent my application data. I am attempting to test the VFP COM object from VFP to make sure it loads ok, that's all.

>
>With VFP, it's VFP all the time. The language, design time tools, and runtime libraries are all intertwined. Visual Studio is simply a design time tool. It has nothing to do with running an application. There are multiple things involved with creating an application with Visual Studio. In fact, you can create .NET applications without Visual Studio and using only free tools.

I'll let the VS guys do their thing...I'm not a .NET programmer...not sure I want to be <g>.

>
>- Visual Studio. The design tool and code editor
>- Language. Generally a .NET language such as C# or VB. Each has it's own compiler that is not part of VS. The C# and VB compilers actually ship as part of the Framework.
>- .NET Framework. A group of classes that can be used by the language. It is separate from the language and VS.
>- .NET runtime. The program created in the language is compiled into a .NET assembly (DLL or EXE) and then executed by the runtime.
>


>Each of these can be shipped on different release schedules. And, in fact, .NET 3.5 was an update to the Framework, runtime, and languages, but not Visual Studio. Microsoft sees these as three different teams, Visual Studio shell (common VS components), Languages, and .NET. Until earlier this week, the .NET team reported to a different person than the other two teams. They now all report to Jason Zander.
>
>So, what I think you're asking is, "What type of COM component can .NET host?" The answer to that question is EXE, DLL, and OCX. VFP cannot create an OCX. Rick Strahl has written a couple of articles about .NET and VFP/COM interop.

That is THE question and the answer you provided is PERFECT!!!!

Thank you, thank you, thank you Craig!

Scott
Previous
Reply
Map
View

Click here to load this message in the networking platform