Groups | Blog | Home
all groups > visual studio .net setup > september 2007 >

visual studio .net setup : CReating Short cut to an application on XP SP2


Sabya
9/10/2007 10:10:00 PM
01. I created a simple VB.NET form (say application X), added a third party
control from Component1, created set up and installed ona XP with SP2
(machine 1).
02. I went to another XP with SP2 (Machine 2) on the LAN, created a a shrot
cut to the folder where the above application X is installed on machine 1.
Wanted to run the application X on machine 2 - did not run - throws an
exception.
03. Installed the Component1 controlon run time on machine 2 - then tried to
run the application X from short cut - does not run.
04. Installed development version of the component1 control on Machine 2 -
tried to run the Application X from short cut - IT RUNS now !

Question - I want to run from short cut without installing the development
version of the component1 control on machine 2 - what is to be done ?

Many thanks in advance for a working response.

Regards
Michel LAPLANE (MVP)
9/11/2007 12:00:00 AM
it seem's that some assembly must be registered to your machine 2 or that
some assembly is missing between your runtime version and your developement
version.

"Sabya" <Sabya@discussions.microsoft.com> a écrit dans le message de
news:288620DE-DFDF-41F4-A681-CF9C0A4E4B59@microsoft.com...
[quoted text, click to view]
Sabya
9/11/2007 5:54:00 AM
Michel,

Thanks for your effort to respond. I have more details and also I want to
correct my earlier observations / add more observations-

01. An application on XP(SP2) machine (MC1) (a development machine) which
has third party controls (ComponentOne) runs well. It is installed on
"D:\SSGINDIA".
02. If I search the MC1 from network places of MC1 and go to D:\SSGINDIA and
try to run the same application - it does not run - displays an exception.
Question is - what is different in this case and what do I do to run it ?
03. I network-map D:\ssgindia as Z: and run the application from Z: - it
does not run. It shows the same exception. What are the issues ?

Probably, if we get the answers to the above, we will get some answers to
the short cut issue. Short cut issue comes at a lower priority - because it
has to run from a different machine. If the application is not running from
the mapped drive on the same machine - we can not think further.

Hope to hear from all soon.

Regards
Sabya

[quoted text, click to view]
Michel LAPLANE (MVP)
9/12/2007 12:00:00 AM
Your component must be register on the running machine. I mean if your
application run on MC2 you must first register the component on the MC2
machine. After that, you could run your application from whatever location
you want.

Two solutions for registering the 3d party component
1. Install the component on MC2 (best and easiest solution)
2. Find the DLL or OCX files of your component that must be registered,
copy theme on MC2 and use regsrv32.exe to register. In case of doubt, try to
register all the files.



"Sabya" <Sabya@discussions.microsoft.com> a écrit dans le message de
news:EE454059-D773-4777-BD65-A853E82B850B@microsoft.com...
[quoted text, click to view]
Sabya
9/12/2007 12:48:03 AM
Michel,

Kindly - Re-Re-read my question - I am talking about only one machine now.
=================Here it goes =============
[quoted text, click to view]

=================Here it ends =============
Thanks for a working response.

Sabya

[quoted text, click to view]
Michel LAPLANE (MVP)
9/13/2007 12:00:00 AM
OK if i understand you are on the same machine and try to run the
application but through a drive connected on the shared directory of the
same machine.

So it does not have anything to do with the registering of the component.

Two ways to investigate.
1. try to run another application from a drive connected to your machine
to a shared place;for example try to run notepad.exe in sharing Windows
directory. If it does not run, the responsible is internet explorer
security. Add your machine to the authorized confident site (Add \\PC1 to
confident sites ; Internet options=>security=>confident site=>Sites).
2. be sure that when you compile, the reference path of the third
component is not hard coded. To test it, try to copy your application to
another directory let say D:\TEST and run it.

Waiting for your response.
"Sabya" <Sabya@discussions.microsoft.com> a écrit dans le message de
news:3E8D1F28-D204-4248-A90D-6FC2E56BE2E4@microsoft.com...
[quoted text, click to view]
AddThis Social Bookmark Button