467,219 Members | 1,361 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,219 developers. It's quick & easy.

Windows form application problem

Hi,

I have just written my first application using VB.NET. The app works fine
when i am running it within .NET for debugging purposes, however when i try
to run the app from the .exe file that .NET creates i get the following
error message:

"An unhandled exception of type 'System.IO.FileNotFoundException' occurred
in VisioTimeline.exe

Additional information: File or assembly name AxInterop.VisOcx, or one of
its dependencies, was not found."

I have tried removing the AxInterop.VisOcx refernce from the app, rebuilding
it then putting the reference back into the solution and rebuilding it again
but i still get the same error.

When the app tries to run and consequently debugs, the disassembly is
displayed but this is in machine code, which although i touched on at uni,
doesn't mean a thing to me.

Can anyone help??

Thanks for any and all help, it is greatly appreciated

reagrds

Lee
Nov 21 '05 #1
  • viewed: 3590
Share:
13 Replies
How is the AxInterop.VisOcx referenced? Are you certain it is in the
correct location for the compiled version of your app?

Do you include it in the setup of your app or have you just compiled the
project and attempted to run the exe from the bin folder?
--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Or**************@TK2MSFTNGP14.phx.gbl...
Hi,

I have just written my first application using VB.NET. The app works fine
when i am running it within .NET for debugging purposes, however when i
try
to run the app from the .exe file that .NET creates i get the following
error message:

"An unhandled exception of type 'System.IO.FileNotFoundException' occurred
in VisioTimeline.exe

Additional information: File or assembly name AxInterop.VisOcx, or one of
its dependencies, was not found."

I have tried removing the AxInterop.VisOcx refernce from the app,
rebuilding
it then putting the reference back into the solution and rebuilding it
again
but i still get the same error.

When the app tries to run and consequently debugs, the disassembly is
displayed but this is in machine code, which although i touched on at uni,
doesn't mean a thing to me.

Can anyone help??

Thanks for any and all help, it is greatly appreciated

reagrds

Lee

Nov 21 '05 #2
Hi Gerry,

It is referenced in the references section of the solution explorer (and i
have referenced it in the coed by "import AxVisOcx =
AxMicrosoft.Office.Interop.VisOcx"

After speaking with a work colleague we think the problem may have something
to do witht he assembly not being in the GAC... when trying to add this
assembly to the GAC i get an error message saying that it is not strongly
named.

I believe that the assembly came with the Visio 2003 SDK.

Unfortunately i do not have any more information. This is the first time i
have created an application using Visual Studio and the first time using hte
Visio ActiveX control so it has got me a little stumped.

Compiling and trying to run the program form the bin folder was the first
thing i did (assuming that it would work). after that i removed the
reference, rebuilt, re-referenced and rebuilt.. still no luck.

Thanks for you help.

regards

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:Oz**************@TK2MSFTNGP10.phx.gbl...
How is the AxInterop.VisOcx referenced? Are you certain it is in the
correct location for the compiled version of your app?

Do you include it in the setup of your app or have you just compiled the
project and attempted to run the exe from the bin folder?
--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Or**************@TK2MSFTNGP14.phx.gbl...
Hi,

I have just written my first application using VB.NET. The app works fine when i am running it within .NET for debugging purposes, however when i
try
to run the app from the .exe file that .NET creates i get the following
error message:

"An unhandled exception of type 'System.IO.FileNotFoundException' occurred in VisioTimeline.exe

Additional information: File or assembly name AxInterop.VisOcx, or one of its dependencies, was not found."

I have tried removing the AxInterop.VisOcx refernce from the app,
rebuilding
it then putting the reference back into the solution and rebuilding it
again
but i still get the same error.

When the app tries to run and consequently debugs, the disassembly is
displayed but this is in machine code, which although i touched on at uni, doesn't mean a thing to me.

Can anyone help??

Thanks for any and all help, it is greatly appreciated

reagrds

Lee


Nov 21 '05 #3
I'm not able to find the ocx in the SDK and I'm not sure you will find and
ActiveX control in the 2003 SDK anyway. Although there is a COM based
object library that installs with the SDK, I cannot locate the control you
are referring to.

I have yet to develop anything in .NET for Visio so I may not the be the
best person to help here but I will try nonetheless.

Here is a for a web site for you to take a look at. Althouth the site is
about C#, the code samples are in VB for this article.

I think you may find part of your answer in the fact that you may not have
run tlbimp.exe on the ocx file to apply a COM wrapper around it.

This article explains how to do just that and then how to isntall it into
the GAC by using the sn.exe utility to create a strongly named assembly.

http://www.csharpfriends.com/Article...x?articleID=43

Hope it helps.

Gerry
"Lee Newson" <le********@hotmail.com> wrote in message
news:u%******************@TK2MSFTNGP10.phx.gbl...
Hi Gerry,

It is referenced in the references section of the solution explorer (and i
have referenced it in the coed by "import AxVisOcx =
AxMicrosoft.Office.Interop.VisOcx"

After speaking with a work colleague we think the problem may have
something
to do witht he assembly not being in the GAC... when trying to add this
assembly to the GAC i get an error message saying that it is not strongly
named.

I believe that the assembly came with the Visio 2003 SDK.

Unfortunately i do not have any more information. This is the first time
i
have created an application using Visual Studio and the first time using
hte
Visio ActiveX control so it has got me a little stumped.

Compiling and trying to run the program form the bin folder was the first
thing i did (assuming that it would work). after that i removed the
reference, rebuilt, re-referenced and rebuilt.. still no luck.

Thanks for you help.

regards

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:Oz**************@TK2MSFTNGP10.phx.gbl...
How is the AxInterop.VisOcx referenced? Are you certain it is in the
correct location for the compiled version of your app?

Do you include it in the setup of your app or have you just compiled the
project and attempted to run the exe from the bin folder?
--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Or**************@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I have just written my first application using VB.NET. The app works fine > when i am running it within .NET for debugging purposes, however when i
> try
> to run the app from the .exe file that .NET creates i get the following
> error message:
>
> "An unhandled exception of type 'System.IO.FileNotFoundException' occurred > in VisioTimeline.exe
>
> Additional information: File or assembly name AxInterop.VisOcx, or one of > its dependencies, was not found."
>
> I have tried removing the AxInterop.VisOcx refernce from the app,
> rebuilding
> it then putting the reference back into the solution and rebuilding it
> again
> but i still get the same error.
>
> When the app tries to run and consequently debugs, the disassembly is
> displayed but this is in machine code, which although i touched on at uni, > doesn't mean a thing to me.
>
> Can anyone help??
>
> Thanks for any and all help, it is greatly appreciated
>
> reagrds
>
> Lee
>
>



Nov 21 '05 #4
Hi Gerry,

I have looked at the article and tried to run the tlbimp.exe on the ocx
file, however i get an error saying that the file is not a valid type
library.

Lee


"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:uW**************@TK2MSFTNGP15.phx.gbl...
I'm not able to find the ocx in the SDK and I'm not sure you will find and
ActiveX control in the 2003 SDK anyway. Although there is a COM based
object library that installs with the SDK, I cannot locate the control you
are referring to.

I have yet to develop anything in .NET for Visio so I may not the be the
best person to help here but I will try nonetheless.

Here is a for a web site for you to take a look at. Althouth the site is
about C#, the code samples are in VB for this article.

I think you may find part of your answer in the fact that you may not have
run tlbimp.exe on the ocx file to apply a COM wrapper around it.

This article explains how to do just that and then how to isntall it into
the GAC by using the sn.exe utility to create a strongly named assembly.

http://www.csharpfriends.com/Article...x?articleID=43

Hope it helps.

Gerry
"Lee Newson" <le********@hotmail.com> wrote in message
news:u%******************@TK2MSFTNGP10.phx.gbl...
Hi Gerry,

It is referenced in the references section of the solution explorer (and i have referenced it in the coed by "import AxVisOcx =
AxMicrosoft.Office.Interop.VisOcx"

After speaking with a work colleague we think the problem may have
something
to do witht he assembly not being in the GAC... when trying to add this
assembly to the GAC i get an error message saying that it is not strongly named.

I believe that the assembly came with the Visio 2003 SDK.

Unfortunately i do not have any more information. This is the first time i
have created an application using Visual Studio and the first time using hte
Visio ActiveX control so it has got me a little stumped.

Compiling and trying to run the program form the bin folder was the first thing i did (assuming that it would work). after that i removed the
reference, rebuilt, re-referenced and rebuilt.. still no luck.

Thanks for you help.

regards

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:Oz**************@TK2MSFTNGP10.phx.gbl...
How is the AxInterop.VisOcx referenced? Are you certain it is in the
correct location for the compiled version of your app?

Do you include it in the setup of your app or have you just compiled the project and attempted to run the exe from the bin folder?
--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Or**************@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I have just written my first application using VB.NET. The app works

fine
> when i am running it within .NET for debugging purposes, however when i > try
> to run the app from the .exe file that .NET creates i get the following > error message:
>
> "An unhandled exception of type 'System.IO.FileNotFoundException'

occurred
> in VisioTimeline.exe
>
> Additional information: File or assembly name AxInterop.VisOcx, or one
of
> its dependencies, was not found."
>
> I have tried removing the AxInterop.VisOcx refernce from the app,
> rebuilding
> it then putting the reference back into the solution and rebuilding

it > again
> but i still get the same error.
>
> When the app tries to run and consequently debugs, the disassembly is
> displayed but this is in machine code, which although i touched on at

uni,
> doesn't mean a thing to me.
>
> Can anyone help??
>
> Thanks for any and all help, it is greatly appreciated
>
> reagrds
>
> Lee
>
>



Nov 21 '05 #5
DOH!

I thought I saw just plain .ocx as the extension. Sorry.

Now I have to try to find that control and see what I can come up with.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:ua**************@TK2MSFTNGP14.phx.gbl...
Hi Gerry,

I have looked at the article and tried to run the tlbimp.exe on the ocx
file, however i get an error saying that the file is not a valid type
library.

Lee


"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:uW**************@TK2MSFTNGP15.phx.gbl...
I'm not able to find the ocx in the SDK and I'm not sure you will find
and
ActiveX control in the 2003 SDK anyway. Although there is a COM based
object library that installs with the SDK, I cannot locate the control
you
are referring to.

I have yet to develop anything in .NET for Visio so I may not the be the
best person to help here but I will try nonetheless.

Here is a for a web site for you to take a look at. Althouth the site is
about C#, the code samples are in VB for this article.

I think you may find part of your answer in the fact that you may not
have
run tlbimp.exe on the ocx file to apply a COM wrapper around it.

This article explains how to do just that and then how to isntall it into
the GAC by using the sn.exe utility to create a strongly named assembly.

http://www.csharpfriends.com/Article...x?articleID=43

Hope it helps.

Gerry
"Lee Newson" <le********@hotmail.com> wrote in message
news:u%******************@TK2MSFTNGP10.phx.gbl...
> Hi Gerry,
>
> It is referenced in the references section of the solution explorer
> (and i > have referenced it in the coed by "import AxVisOcx =
> AxMicrosoft.Office.Interop.VisOcx"
>
> After speaking with a work colleague we think the problem may have
> something
> to do witht he assembly not being in the GAC... when trying to add this
> assembly to the GAC i get an error message saying that it is not strongly > named.
>
> I believe that the assembly came with the Visio 2003 SDK.
>
> Unfortunately i do not have any more information. This is the first time > i
> have created an application using Visual Studio and the first time
> using > hte
> Visio ActiveX control so it has got me a little stumped.
>
> Compiling and trying to run the program form the bin folder was the first > thing i did (assuming that it would work). after that i removed the
> reference, rebuilt, re-referenced and rebuilt.. still no luck.
>
> Thanks for you help.
>
> regards
>
> Lee
>
>
>
> "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> news:Oz**************@TK2MSFTNGP10.phx.gbl...
>> How is the AxInterop.VisOcx referenced? Are you certain it is in the
>> correct location for the compiled version of your app?
>>
>> Do you include it in the setup of your app or have you just compiled the >> project and attempted to run the exe from the bin folder?
>>
>>
>> --
>> Gerry O'Brien
>> Visual Basic.NET MVP
>>
>>
>> "Lee Newson" <le********@hotmail.com> wrote in message
>> news:Or**************@TK2MSFTNGP14.phx.gbl...
>> > Hi,
>> >
>> > I have just written my first application using VB.NET. The app works
> fine
>> > when i am running it within .NET for debugging purposes, however
>> > when i >> > try
>> > to run the app from the .exe file that .NET creates i get the following >> > error message:
>> >
>> > "An unhandled exception of type 'System.IO.FileNotFoundException'
> occurred
>> > in VisioTimeline.exe
>> >
>> > Additional information: File or assembly name AxInterop.VisOcx, or one > of
>> > its dependencies, was not found."
>> >
>> > I have tried removing the AxInterop.VisOcx refernce from the app,
>> > rebuilding
>> > it then putting the reference back into the solution and rebuilding it >> > again
>> > but i still get the same error.
>> >
>> > When the app tries to run and consequently debugs, the disassembly
>> > is
>> > displayed but this is in machine code, which although i touched on
>> > at
> uni,
>> > doesn't mean a thing to me.
>> >
>> > Can anyone help??
>> >
>> > Thanks for any and all help, it is greatly appreciated
>> >
>> > reagrds
>> >
>> > Lee
>> >
>> >
>>
>>
>
>



Nov 21 '05 #6
Hi Gerry,

I have just tried creating a basic form that only has the Visio Drawing
control on it... to do this i added the component to the form toolbox (this
is the Microsoft.Office.Interop.VisOcx.dll type library) when i add the
drawing control to the form it seems to automatically create the
AxInterop.VisOcx.dll file... and it is this file that is causing the problem
when i try to run the compiled exe.

lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:%2*****************@TK2MSFTNGP14.phx.gbl...
DOH!

I thought I saw just plain .ocx as the extension. Sorry.

Now I have to try to find that control and see what I can come up with.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:ua**************@TK2MSFTNGP14.phx.gbl...
Hi Gerry,

I have looked at the article and tried to run the tlbimp.exe on the ocx
file, however i get an error saying that the file is not a valid type
library.

Lee


"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:uW**************@TK2MSFTNGP15.phx.gbl...
I'm not able to find the ocx in the SDK and I'm not sure you will find
and
ActiveX control in the 2003 SDK anyway. Although there is a COM based
object library that installs with the SDK, I cannot locate the control
you
are referring to.

I have yet to develop anything in .NET for Visio so I may not the be the best person to help here but I will try nonetheless.

Here is a for a web site for you to take a look at. Althouth the site is about C#, the code samples are in VB for this article.

I think you may find part of your answer in the fact that you may not
have
run tlbimp.exe on the ocx file to apply a COM wrapper around it.

This article explains how to do just that and then how to isntall it into the GAC by using the sn.exe utility to create a strongly named assembly.
http://www.csharpfriends.com/Article...x?articleID=43

Hope it helps.

Gerry
"Lee Newson" <le********@hotmail.com> wrote in message
news:u%******************@TK2MSFTNGP10.phx.gbl...
> Hi Gerry,
>
> It is referenced in the references section of the solution explorer
> (and

i
> have referenced it in the coed by "import AxVisOcx =
> AxMicrosoft.Office.Interop.VisOcx"
>
> After speaking with a work colleague we think the problem may have
> something
> to do witht he assembly not being in the GAC... when trying to add this > assembly to the GAC i get an error message saying that it is not

strongly
> named.
>
> I believe that the assembly came with the Visio 2003 SDK.
>
> Unfortunately i do not have any more information. This is the first

time
> i
> have created an application using Visual Studio and the first time
> using

> hte
> Visio ActiveX control so it has got me a little stumped.
>
> Compiling and trying to run the program form the bin folder was the

first
> thing i did (assuming that it would work). after that i removed the
> reference, rebuilt, re-referenced and rebuilt.. still no luck.
>
> Thanks for you help.
>
> regards
>
> Lee
>
>
>
> "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> news:Oz**************@TK2MSFTNGP10.phx.gbl...
>> How is the AxInterop.VisOcx referenced? Are you certain it is in the >> correct location for the compiled version of your app?
>>
>> Do you include it in the setup of your app or have you just compiled

the
>> project and attempted to run the exe from the bin folder?
>>
>>
>> --
>> Gerry O'Brien
>> Visual Basic.NET MVP
>>
>>
>> "Lee Newson" <le********@hotmail.com> wrote in message
>> news:Or**************@TK2MSFTNGP14.phx.gbl...
>> > Hi,
>> >
>> > I have just written my first application using VB.NET. The app works > fine
>> > when i am running it within .NET for debugging purposes, however
>> > when

i
>> > try
>> > to run the app from the .exe file that .NET creates i get the

following
>> > error message:
>> >
>> > "An unhandled exception of type 'System.IO.FileNotFoundException'
> occurred
>> > in VisioTimeline.exe
>> >
>> > Additional information: File or assembly name AxInterop.VisOcx, or

one
> of
>> > its dependencies, was not found."
>> >
>> > I have tried removing the AxInterop.VisOcx refernce from the app,
>> > rebuilding
>> > it then putting the reference back into the solution and
rebuilding it
>> > again
>> > but i still get the same error.
>> >
>> > When the app tries to run and consequently debugs, the disassembly
>> > is
>> > displayed but this is in machine code, which although i touched on
>> > at
> uni,
>> > doesn't mean a thing to me.
>> >
>> > Can anyone help??
>> >
>> > Thanks for any and all help, it is greatly appreciated
>> >
>> > reagrds
>> >
>> > Lee
>> >
>> >
>>
>>
>
>



Nov 21 '05 #7
Ok, again partly my own stupidity on this one. I was looking at adding a
reference in the referece section manually.

Instead, I added the control to the toolbox. Dropped it on the form and
here is what is in my references section;

AxVisOcx
Visio
VisOcx

I'm not doing anything with the control at all, just placed it on the form.

Ran the app from the IDE, it opens and displays the Visio drawing window.

Compiled the app, ran the exe from the bin/debug folder, and all works well.

I notice that the AxInterop.VisOcx.dll is in the bin/debug folder. Is
yours?

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Oh*************@TK2MSFTNGP15.phx.gbl...
Hi Gerry,

I have just tried creating a basic form that only has the Visio Drawing
control on it... to do this i added the component to the form toolbox
(this
is the Microsoft.Office.Interop.VisOcx.dll type library) when i add the
drawing control to the form it seems to automatically create the
AxInterop.VisOcx.dll file... and it is this file that is causing the
problem
when i try to run the compiled exe.

lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:%2*****************@TK2MSFTNGP14.phx.gbl...
DOH!

I thought I saw just plain .ocx as the extension. Sorry.

Now I have to try to find that control and see what I can come up with.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:ua**************@TK2MSFTNGP14.phx.gbl...
> Hi Gerry,
>
> I have looked at the article and tried to run the tlbimp.exe on the ocx
> file, however i get an error saying that the file is not a valid type
> library.
>
> Lee
>
>
>
>
> "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> news:uW**************@TK2MSFTNGP15.phx.gbl...
>> I'm not able to find the ocx in the SDK and I'm not sure you will find
>> and
>> ActiveX control in the 2003 SDK anyway. Although there is a COM based
>> object library that installs with the SDK, I cannot locate the control
>> you
>> are referring to.
>>
>> I have yet to develop anything in .NET for Visio so I may not the be the >> best person to help here but I will try nonetheless.
>>
>> Here is a for a web site for you to take a look at. Althouth the site is >> about C#, the code samples are in VB for this article.
>>
>> I think you may find part of your answer in the fact that you may not
>> have
>> run tlbimp.exe on the ocx file to apply a COM wrapper around it.
>>
>> This article explains how to do just that and then how to isntall it into >> the GAC by using the sn.exe utility to create a strongly named assembly. >>
>> http://www.csharpfriends.com/Article...x?articleID=43
>>
>> Hope it helps.
>>
>> Gerry
>>
>>
>> "Lee Newson" <le********@hotmail.com> wrote in message
>> news:u%******************@TK2MSFTNGP10.phx.gbl...
>> > Hi Gerry,
>> >
>> > It is referenced in the references section of the solution explorer
>> > (and
> i
>> > have referenced it in the coed by "import AxVisOcx =
>> > AxMicrosoft.Office.Interop.VisOcx"
>> >
>> > After speaking with a work colleague we think the problem may have
>> > something
>> > to do witht he assembly not being in the GAC... when trying to add this >> > assembly to the GAC i get an error message saying that it is not
> strongly
>> > named.
>> >
>> > I believe that the assembly came with the Visio 2003 SDK.
>> >
>> > Unfortunately i do not have any more information. This is the first
> time
>> > i
>> > have created an application using Visual Studio and the first time
>> > using
>
>> > hte
>> > Visio ActiveX control so it has got me a little stumped.
>> >
>> > Compiling and trying to run the program form the bin folder was the
> first
>> > thing i did (assuming that it would work). after that i removed the
>> > reference, rebuilt, re-referenced and rebuilt.. still no luck.
>> >
>> > Thanks for you help.
>> >
>> > regards
>> >
>> > Lee
>> >
>> >
>> >
>> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
>> >> How is the AxInterop.VisOcx referenced? Are you certain it is in the >> >> correct location for the compiled version of your app?
>> >>
>> >> Do you include it in the setup of your app or have you just
>> >> compiled
> the
>> >> project and attempted to run the exe from the bin folder?
>> >>
>> >>
>> >> --
>> >> Gerry O'Brien
>> >> Visual Basic.NET MVP
>> >>
>> >>
>> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > I have just written my first application using VB.NET. The app works >> > fine
>> >> > when i am running it within .NET for debugging purposes, however
>> >> > when
> i
>> >> > try
>> >> > to run the app from the .exe file that .NET creates i get the
> following
>> >> > error message:
>> >> >
>> >> > "An unhandled exception of type 'System.IO.FileNotFoundException'
>> > occurred
>> >> > in VisioTimeline.exe
>> >> >
>> >> > Additional information: File or assembly name AxInterop.VisOcx,
>> >> > or
> one
>> > of
>> >> > its dependencies, was not found."
>> >> >
>> >> > I have tried removing the AxInterop.VisOcx refernce from the app,
>> >> > rebuilding
>> >> > it then putting the reference back into the solution and rebuilding > it
>> >> > again
>> >> > but i still get the same error.
>> >> >
>> >> > When the app tries to run and consequently debugs, the
>> >> > disassembly
>> >> > is
>> >> > displayed but this is in machine code, which although i touched
>> >> > on
>> >> > at
>> > uni,
>> >> > doesn't mean a thing to me.
>> >> >
>> >> > Can anyone help??
>> >> >
>> >> > Thanks for any and all help, it is greatly appreciated
>> >> >
>> >> > reagrds
>> >> >
>> >> > Lee
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>



Nov 21 '05 #8
Yes, this file does get created in the bin folder, the problem comes when i
try to deply the app to a different machine which has the .NET
redistibutable package installed.

I am wondering now if somehow i have to change the path to the file from
f:\...\bin\AxInterop.VisOcx.dll to something else... but i am unsure... as i
said initially this is the first time i have created either a windows app or
programmed using the visio drawing control.

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:ur**************@tk2msftngp13.phx.gbl...
Ok, again partly my own stupidity on this one. I was looking at adding a
reference in the referece section manually.

Instead, I added the control to the toolbox. Dropped it on the form and
here is what is in my references section;

AxVisOcx
Visio
VisOcx

I'm not doing anything with the control at all, just placed it on the form.
Ran the app from the IDE, it opens and displays the Visio drawing window.

Compiled the app, ran the exe from the bin/debug folder, and all works well.
I notice that the AxInterop.VisOcx.dll is in the bin/debug folder. Is
yours?

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Oh*************@TK2MSFTNGP15.phx.gbl...
Hi Gerry,

I have just tried creating a basic form that only has the Visio Drawing
control on it... to do this i added the component to the form toolbox
(this
is the Microsoft.Office.Interop.VisOcx.dll type library) when i add the
drawing control to the form it seems to automatically create the
AxInterop.VisOcx.dll file... and it is this file that is causing the
problem
when i try to run the compiled exe.

lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:%2*****************@TK2MSFTNGP14.phx.gbl...
DOH!

I thought I saw just plain .ocx as the extension. Sorry.

Now I have to try to find that control and see what I can come up with.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:ua**************@TK2MSFTNGP14.phx.gbl...
> Hi Gerry,
>
> I have looked at the article and tried to run the tlbimp.exe on the ocx > file, however i get an error saying that the file is not a valid type
> library.
>
> Lee
>
>
>
>
> "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> news:uW**************@TK2MSFTNGP15.phx.gbl...
>> I'm not able to find the ocx in the SDK and I'm not sure you will find >> and
>> ActiveX control in the 2003 SDK anyway. Although there is a COM based >> object library that installs with the SDK, I cannot locate the control >> you
>> are referring to.
>>
>> I have yet to develop anything in .NET for Visio so I may not the be

the
>> best person to help here but I will try nonetheless.
>>
>> Here is a for a web site for you to take a look at. Althouth the site
is
>> about C#, the code samples are in VB for this article.
>>
>> I think you may find part of your answer in the fact that you may

not >> have
>> run tlbimp.exe on the ocx file to apply a COM wrapper around it.
>>
>> This article explains how to do just that and then how to isntall it

into
>> the GAC by using the sn.exe utility to create a strongly named

assembly.
>>
>> http://www.csharpfriends.com/Article...x?articleID=43
>>
>> Hope it helps.
>>
>> Gerry
>>
>>
>> "Lee Newson" <le********@hotmail.com> wrote in message
>> news:u%******************@TK2MSFTNGP10.phx.gbl...
>> > Hi Gerry,
>> >
>> > It is referenced in the references section of the solution explorer >> > (and
> i
>> > have referenced it in the coed by "import AxVisOcx =
>> > AxMicrosoft.Office.Interop.VisOcx"
>> >
>> > After speaking with a work colleague we think the problem may have
>> > something
>> > to do witht he assembly not being in the GAC... when trying to add

this
>> > assembly to the GAC i get an error message saying that it is not
> strongly
>> > named.
>> >
>> > I believe that the assembly came with the Visio 2003 SDK.
>> >
>> > Unfortunately i do not have any more information. This is the first > time
>> > i
>> > have created an application using Visual Studio and the first time
>> > using
>
>> > hte
>> > Visio ActiveX control so it has got me a little stumped.
>> >
>> > Compiling and trying to run the program form the bin folder was the > first
>> > thing i did (assuming that it would work). after that i removed the >> > reference, rebuilt, re-referenced and rebuilt.. still no luck.
>> >
>> > Thanks for you help.
>> >
>> > regards
>> >
>> > Lee
>> >
>> >
>> >
>> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
>> >> How is the AxInterop.VisOcx referenced? Are you certain it is in

the
>> >> correct location for the compiled version of your app?
>> >>
>> >> Do you include it in the setup of your app or have you just
>> >> compiled
> the
>> >> project and attempted to run the exe from the bin folder?
>> >>
>> >>
>> >> --
>> >> Gerry O'Brien
>> >> Visual Basic.NET MVP
>> >>
>> >>
>> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > I have just written my first application using VB.NET. The app

works
>> > fine
>> >> > when i am running it within .NET for debugging purposes, however >> >> > when
> i
>> >> > try
>> >> > to run the app from the .exe file that .NET creates i get the
> following
>> >> > error message:
>> >> >
>> >> > "An unhandled exception of type 'System.IO.FileNotFoundException' >> > occurred
>> >> > in VisioTimeline.exe
>> >> >
>> >> > Additional information: File or assembly name AxInterop.VisOcx,
>> >> > or
> one
>> > of
>> >> > its dependencies, was not found."
>> >> >
>> >> > I have tried removing the AxInterop.VisOcx refernce from the app, >> >> > rebuilding
>> >> > it then putting the reference back into the solution and

rebuilding
> it
>> >> > again
>> >> > but i still get the same error.
>> >> >
>> >> > When the app tries to run and consequently debugs, the
>> >> > disassembly
>> >> > is
>> >> > displayed but this is in machine code, which although i touched
>> >> > on
>> >> > at
>> > uni,
>> >> > doesn't mean a thing to me.
>> >> >
>> >> > Can anyone help??
>> >> >
>> >> > Thanks for any and all help, it is greatly appreciated
>> >> >
>> >> > reagrds
>> >> >
>> >> > Lee
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>



Nov 21 '05 #9
Just make sure that you have actually added that file in setup project so
that it will be copied to the correct folder when the app is deployed on
another machine. That is likely the problem you are having.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:OR*************@TK2MSFTNGP15.phx.gbl...
Yes, this file does get created in the bin folder, the problem comes when
i
try to deply the app to a different machine which has the .NET
redistibutable package installed.

I am wondering now if somehow i have to change the path to the file from
f:\...\bin\AxInterop.VisOcx.dll to something else... but i am unsure... as
i
said initially this is the first time i have created either a windows app
or
programmed using the visio drawing control.

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:ur**************@tk2msftngp13.phx.gbl...
Ok, again partly my own stupidity on this one. I was looking at adding a
reference in the referece section manually.

Instead, I added the control to the toolbox. Dropped it on the form and
here is what is in my references section;

AxVisOcx
Visio
VisOcx

I'm not doing anything with the control at all, just placed it on the

form.

Ran the app from the IDE, it opens and displays the Visio drawing window.

Compiled the app, ran the exe from the bin/debug folder, and all works

well.

I notice that the AxInterop.VisOcx.dll is in the bin/debug folder. Is
yours?

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Oh*************@TK2MSFTNGP15.phx.gbl...
> Hi Gerry,
>
> I have just tried creating a basic form that only has the Visio Drawing
> control on it... to do this i added the component to the form toolbox
> (this
> is the Microsoft.Office.Interop.VisOcx.dll type library) when i add the
> drawing control to the form it seems to automatically create the
> AxInterop.VisOcx.dll file... and it is this file that is causing the
> problem
> when i try to run the compiled exe.
>
>
>
> lee
>
>
>
>
>
> "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> news:%2*****************@TK2MSFTNGP14.phx.gbl...
>> DOH!
>>
>> I thought I saw just plain .ocx as the extension. Sorry.
>>
>> Now I have to try to find that control and see what I can come up
>> with.
>>
>> --
>> Gerry O'Brien
>> Visual Basic.NET MVP
>>
>>
>> "Lee Newson" <le********@hotmail.com> wrote in message
>> news:ua**************@TK2MSFTNGP14.phx.gbl...
>> > Hi Gerry,
>> >
>> > I have looked at the article and tried to run the tlbimp.exe on the ocx >> > file, however i get an error saying that the file is not a valid
>> > type
>> > library.
>> >
>> > Lee
>> >
>> >
>> >
>> >
>> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > news:uW**************@TK2MSFTNGP15.phx.gbl...
>> >> I'm not able to find the ocx in the SDK and I'm not sure you will find >> >> and
>> >> ActiveX control in the 2003 SDK anyway. Although there is a COM based >> >> object library that installs with the SDK, I cannot locate the control >> >> you
>> >> are referring to.
>> >>
>> >> I have yet to develop anything in .NET for Visio so I may not the
>> >> be
> the
>> >> best person to help here but I will try nonetheless.
>> >>
>> >> Here is a for a web site for you to take a look at. Althouth the site > is
>> >> about C#, the code samples are in VB for this article.
>> >>
>> >> I think you may find part of your answer in the fact that you may not >> >> have
>> >> run tlbimp.exe on the ocx file to apply a COM wrapper around it.
>> >>
>> >> This article explains how to do just that and then how to isntall
>> >> it
> into
>> >> the GAC by using the sn.exe utility to create a strongly named
> assembly.
>> >>
>> >> http://www.csharpfriends.com/Article...x?articleID=43
>> >>
>> >> Hope it helps.
>> >>
>> >> Gerry
>> >>
>> >>
>> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> >> news:u%******************@TK2MSFTNGP10.phx.gbl...
>> >> > Hi Gerry,
>> >> >
>> >> > It is referenced in the references section of the solution explorer >> >> > (and
>> > i
>> >> > have referenced it in the coed by "import AxVisOcx =
>> >> > AxMicrosoft.Office.Interop.VisOcx"
>> >> >
>> >> > After speaking with a work colleague we think the problem may
>> >> > have
>> >> > something
>> >> > to do witht he assembly not being in the GAC... when trying to
>> >> > add
> this
>> >> > assembly to the GAC i get an error message saying that it is not
>> > strongly
>> >> > named.
>> >> >
>> >> > I believe that the assembly came with the Visio 2003 SDK.
>> >> >
>> >> > Unfortunately i do not have any more information. This is the first >> > time
>> >> > i
>> >> > have created an application using Visual Studio and the first
>> >> > time
>> >> > using
>> >
>> >> > hte
>> >> > Visio ActiveX control so it has got me a little stumped.
>> >> >
>> >> > Compiling and trying to run the program form the bin folder was the >> > first
>> >> > thing i did (assuming that it would work). after that i removed the >> >> > reference, rebuilt, re-referenced and rebuilt.. still no luck.
>> >> >
>> >> > Thanks for you help.
>> >> >
>> >> > regards
>> >> >
>> >> > Lee
>> >> >
>> >> >
>> >> >
>> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> >> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
>> >> >> How is the AxInterop.VisOcx referenced? Are you certain it is
>> >> >> in
> the
>> >> >> correct location for the compiled version of your app?
>> >> >>
>> >> >> Do you include it in the setup of your app or have you just
>> >> >> compiled
>> > the
>> >> >> project and attempted to run the exe from the bin folder?
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Gerry O'Brien
>> >> >> Visual Basic.NET MVP
>> >> >>
>> >> >>
>> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> >> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
>> >> >> > Hi,
>> >> >> >
>> >> >> > I have just written my first application using VB.NET. The app
> works
>> >> > fine
>> >> >> > when i am running it within .NET for debugging purposes, however >> >> >> > when
>> > i
>> >> >> > try
>> >> >> > to run the app from the .exe file that .NET creates i get the
>> > following
>> >> >> > error message:
>> >> >> >
>> >> >> > "An unhandled exception of type 'System.IO.FileNotFoundException' >> >> > occurred
>> >> >> > in VisioTimeline.exe
>> >> >> >
>> >> >> > Additional information: File or assembly name
>> >> >> > AxInterop.VisOcx,
>> >> >> > or
>> > one
>> >> > of
>> >> >> > its dependencies, was not found."
>> >> >> >
>> >> >> > I have tried removing the AxInterop.VisOcx refernce from the app, >> >> >> > rebuilding
>> >> >> > it then putting the reference back into the solution and
> rebuilding
>> > it
>> >> >> > again
>> >> >> > but i still get the same error.
>> >> >> >
>> >> >> > When the app tries to run and consequently debugs, the
>> >> >> > disassembly
>> >> >> > is
>> >> >> > displayed but this is in machine code, which although i
>> >> >> > touched
>> >> >> > on
>> >> >> > at
>> >> > uni,
>> >> >> > doesn't mean a thing to me.
>> >> >> >
>> >> >> > Can anyone help??
>> >> >> >
>> >> >> > Thanks for any and all help, it is greatly appreciated
>> >> >> >
>> >> >> > reagrds
>> >> >> >
>> >> >> > Lee
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>



Nov 21 '05 #10
Hi Gerry,

I think i may have found the problem... it would appear that the app will
only work if the other machine has VS.NET installed, it will not work in the
VS.NET redistributable package is installed... this is a problem in itself
because from my understanding we will need to get another license for .NET
to install it on the machine that my app needs to run on.

It also means that i am going to have to seperate the two modes of the
program so that the admin side cacn be used on our project managers
machines... this is not the ideal situation to be in and i can't for the
life of me understand why the app needs the full install of VS.NET to run.

I don't suppose you have any ideas why this might be the case?? or how to
solve it?

If not then thank you very much for your help with this it is has been very
appreciated.

regards

Lee


"Lee Newson" <le********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi Gerry,

I have checked all the files in the setup project and the
AxInterop.VisOcx.dll file is in it.
The app has two ways to run. Automatically create the timelines (no user
interaction with the app) and the admin side where the user can define what timelines to create - which schedules to include from project server and
various other settings.

When i run the auto mode it just falls over with the system.io.filenotfound, when i run it in admin mode i get the error (see attached txt file).

It would appear for whatever reason that the app cannot load the
AxInterop.VisOcx assembly.

I have also tried creating the project from scratch, adding the existing
code files etc and using all the default VS.NET properties etc, still no
luck. When i did this i had to drop the drawing control on the form again, and the AxInterop.VisOcx.dll file was created and i have not touched any of the settings for this.

The program runs absolutely fine on my machine the problem is still
deploying it to another machine (i used the setup wizard for this to create a setup project), all the files are included in this and are installed to
the other machine during setup.

Lee





"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:ep*************@TK2MSFTNGP10.phx.gbl...
Just make sure that you have actually added that file in setup project so
that it will be copied to the correct folder when the app is deployed on
another machine. That is likely the problem you are having.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:OR*************@TK2MSFTNGP15.phx.gbl...
Yes, this file does get created in the bin folder, the problem comes
when i
try to deply the app to a different machine which has the .NET
redistibutable package installed.

I am wondering now if somehow i have to change the path to the file from f:\...\bin\AxInterop.VisOcx.dll to something else... but i am unsure... as
i
said initially this is the first time i have created either a windows app or
programmed using the visio drawing control.

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:ur**************@tk2msftngp13.phx.gbl...
> Ok, again partly my own stupidity on this one. I was looking at
adding
a> reference in the referece section manually.
>
> Instead, I added the control to the toolbox. Dropped it on the form and> here is what is in my references section;
>
> AxVisOcx
> Visio
> VisOcx
>
> I'm not doing anything with the control at all, just placed it on the
form.
>
> Ran the app from the IDE, it opens and displays the Visio drawing window.>
> Compiled the app, ran the exe from the bin/debug folder, and all
works well.
>
> I notice that the AxInterop.VisOcx.dll is in the bin/debug folder. Is> yours?
>
>
>
> --
> Gerry O'Brien
> Visual Basic.NET MVP
>
>
> "Lee Newson" <le********@hotmail.com> wrote in message
> news:Oh*************@TK2MSFTNGP15.phx.gbl...
> > Hi Gerry,
> >
> > I have just tried creating a basic form that only has the Visio

Drawing> > control on it... to do this i added the component to the form toolbox> > (this
> > is the Microsoft.Office.Interop.VisOcx.dll type library) when i add the> > drawing control to the form it seems to automatically create the
> > AxInterop.VisOcx.dll file... and it is this file that is causing the> > problem
> > when i try to run the compiled exe.
> >
> >
> >
> > lee
> >
> >
> >
> >
> >
> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> > news:%2*****************@TK2MSFTNGP14.phx.gbl...
> >> DOH!
> >>
> >> I thought I saw just plain .ocx as the extension. Sorry.
> >>
> >> Now I have to try to find that control and see what I can come up
> >> with.
> >>
> >> --
> >> Gerry O'Brien
> >> Visual Basic.NET MVP
> >>
> >>
> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> news:ua**************@TK2MSFTNGP14.phx.gbl...
> >> > Hi Gerry,
> >> >
> >> > I have looked at the article and tried to run the tlbimp.exe on the ocx
> >> > file, however i get an error saying that the file is not a valid
> >> > type
> >> > library.
> >> >
> >> > Lee
> >> >
> >> >
> >> >
> >> >
> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> > news:uW**************@TK2MSFTNGP15.phx.gbl...
> >> >> I'm not able to find the ocx in the SDK and I'm not sure you will find
> >> >> and
> >> >> ActiveX control in the 2003 SDK anyway. Although there is a COM based
> >> >> object library that installs with the SDK, I cannot locate the
control
> >> >> you
> >> >> are referring to.
> >> >>
> >> >> I have yet to develop anything in .NET for Visio so I may not the> >> >> be
> > the
> >> >> best person to help here but I will try nonetheless.
> >> >>
> >> >> Here is a for a web site for you to take a look at. Althouth the site
> > is
> >> >> about C#, the code samples are in VB for this article.
> >> >>
> >> >> I think you may find part of your answer in the fact that you may not
> >> >> have
> >> >> run tlbimp.exe on the ocx file to apply a COM wrapper around it.> >> >>
> >> >> This article explains how to do just that and then how to isntall> >> >> it
> > into
> >> >> the GAC by using the sn.exe utility to create a strongly named
> > assembly.
> >> >>
> >> >> http://www.csharpfriends.com/Article...x?articleID=43> >> >>
> >> >> Hope it helps.
> >> >>
> >> >> Gerry
> >> >>
> >> >>
> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> news:u%******************@TK2MSFTNGP10.phx.gbl...
> >> >> > Hi Gerry,
> >> >> >
> >> >> > It is referenced in the references section of the solution
explorer
> >> >> > (and
> >> > i
> >> >> > have referenced it in the coed by "import AxVisOcx =
> >> >> > AxMicrosoft.Office.Interop.VisOcx"
> >> >> >
> >> >> > After speaking with a work colleague we think the problem may
> >> >> > have
> >> >> > something
> >> >> > to do witht he assembly not being in the GAC... when trying to> >> >> > add
> > this
> >> >> > assembly to the GAC i get an error message saying that it is not> >> > strongly
> >> >> > named.
> >> >> >
> >> >> > I believe that the assembly came with the Visio 2003 SDK.
> >> >> >
> >> >> > Unfortunately i do not have any more information. This is the first
> >> > time
> >> >> > i
> >> >> > have created an application using Visual Studio and the first
> >> >> > time
> >> >> > using
> >> >
> >> >> > hte
> >> >> > Visio ActiveX control so it has got me a little stumped.
> >> >> >
> >> >> > Compiling and trying to run the program form the bin folder was the
> >> > first
> >> >> > thing i did (assuming that it would work). after that i removed the
> >> >> > reference, rebuilt, re-referenced and rebuilt.. still no luck.> >> >> >
> >> >> > Thanks for you help.
> >> >> >
> >> >> > regards
> >> >> >
> >> >> > Lee
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> >> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
> >> >> >> How is the AxInterop.VisOcx referenced? Are you certain it is> >> >> >> in
> > the
> >> >> >> correct location for the compiled version of your app?
> >> >> >>
> >> >> >> Do you include it in the setup of your app or have you just
> >> >> >> compiled
> >> > the
> >> >> >> project and attempted to run the exe from the bin folder?
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Gerry O'Brien
> >> >> >> Visual Basic.NET MVP
> >> >> >>
> >> >> >>
> >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
> >> >> >> > Hi,
> >> >> >> >
> >> >> >> > I have just written my first application using VB.NET. The app> > works
> >> >> > fine
> >> >> >> > when i am running it within .NET for debugging purposes,
however
> >> >> >> > when
> >> > i
> >> >> >> > try
> >> >> >> > to run the app from the .exe file that .NET creates i get the> >> > following
> >> >> >> > error message:
> >> >> >> >
> >> >> >> > "An unhandled exception of type
'System.IO.FileNotFoundException'
> >> >> > occurred
> >> >> >> > in VisioTimeline.exe
> >> >> >> >
> >> >> >> > Additional information: File or assembly name
> >> >> >> > AxInterop.VisOcx,
> >> >> >> > or
> >> > one
> >> >> > of
> >> >> >> > its dependencies, was not found."
> >> >> >> >
> >> >> >> > I have tried removing the AxInterop.VisOcx refernce from the app,
> >> >> >> > rebuilding
> >> >> >> > it then putting the reference back into the solution and
> > rebuilding
> >> > it
> >> >> >> > again
> >> >> >> > but i still get the same error.
> >> >> >> >
> >> >> >> > When the app tries to run and consequently debugs, the
> >> >> >> > disassembly
> >> >> >> > is
> >> >> >> > displayed but this is in machine code, which although i
> >> >> >> > touched
> >> >> >> > on
> >> >> >> > at
> >> >> > uni,
> >> >> >> > doesn't mean a thing to me.
> >> >> >> >
> >> >> >> > Can anyone help??
> >> >> >> >
> >> >> >> > Thanks for any and all help, it is greatly appreciated
> >> >> >> >
> >> >> >> > reagrds
> >> >> >> >
> >> >> >> > Lee
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>



Nov 21 '05 #11
Interesting. I have never heard of that scenario before.

I hope it does solve your issue though.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Oh**************@tk2msftngp13.phx.gbl...
Hi Gerry,

I think i may have found the problem... it would appear that the app will
only work if the other machine has VS.NET installed, it will not work in
the
VS.NET redistributable package is installed... this is a problem in itself
because from my understanding we will need to get another license for .NET
to install it on the machine that my app needs to run on.

It also means that i am going to have to seperate the two modes of the
program so that the admin side cacn be used on our project managers
machines... this is not the ideal situation to be in and i can't for the
life of me understand why the app needs the full install of VS.NET to run.

I don't suppose you have any ideas why this might be the case?? or how to
solve it?

If not then thank you very much for your help with this it is has been
very
appreciated.

regards

Lee


"Lee Newson" <le********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi Gerry,

I have checked all the files in the setup project and the
AxInterop.VisOcx.dll file is in it.
The app has two ways to run. Automatically create the timelines (no user
interaction with the app) and the admin side where the user can define

what
timelines to create - which schedules to include from project server and
various other settings.

When i run the auto mode it just falls over with the

system.io.filenotfound,
when i run it in admin mode i get the error (see attached txt file).

It would appear for whatever reason that the app cannot load the
AxInterop.VisOcx assembly.

I have also tried creating the project from scratch, adding the existing
code files etc and using all the default VS.NET properties etc, still no
luck. When i did this i had to drop the drawing control on the form

again,
and the AxInterop.VisOcx.dll file was created and i have not touched any

of
the settings for this.

The program runs absolutely fine on my machine the problem is still
deploying it to another machine (i used the setup wizard for this to

create
a setup project), all the files are included in this and are installed to
the other machine during setup.

Lee





"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:ep*************@TK2MSFTNGP10.phx.gbl...
> Just make sure that you have actually added that file in setup project so > that it will be copied to the correct folder when the app is deployed
> on
> another machine. That is likely the problem you are having.
>
> --
> Gerry O'Brien
> Visual Basic.NET MVP
>
>
> "Lee Newson" <le********@hotmail.com> wrote in message
> news:OR*************@TK2MSFTNGP15.phx.gbl...
> > Yes, this file does get created in the bin folder, the problem comes

when
> > i
> > try to deply the app to a different machine which has the .NET
> > redistibutable package installed.
> >
> > I am wondering now if somehow i have to change the path to the file from > > f:\...\bin\AxInterop.VisOcx.dll to something else... but i am unsure...
as
> > i
> > said initially this is the first time i have created either a windows

app
> > or
> > programmed using the visio drawing control.
> >
> > Lee
> >
> >
> >
> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> > news:ur**************@tk2msftngp13.phx.gbl...
> >> Ok, again partly my own stupidity on this one. I was looking at

adding
a
> >> reference in the referece section manually.
> >>
> >> Instead, I added the control to the toolbox. Dropped it on the form

and
> >> here is what is in my references section;
> >>
> >> AxVisOcx
> >> Visio
> >> VisOcx
> >>
> >> I'm not doing anything with the control at all, just placed it on
> >> the
> > form.
> >>
> >> Ran the app from the IDE, it opens and displays the Visio drawing

window.
> >>
> >> Compiled the app, ran the exe from the bin/debug folder, and all

works > > well.
> >>
> >> I notice that the AxInterop.VisOcx.dll is in the bin/debug folder. Is > >> yours?
> >>
> >>
> >>
> >> --
> >> Gerry O'Brien
> >> Visual Basic.NET MVP
> >>
> >>
> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> news:Oh*************@TK2MSFTNGP15.phx.gbl...
> >> > Hi Gerry,
> >> >
> >> > I have just tried creating a basic form that only has the Visio

Drawing
> >> > control on it... to do this i added the component to the form toolbox > >> > (this
> >> > is the Microsoft.Office.Interop.VisOcx.dll type library) when i
> >> > add

the
> >> > drawing control to the form it seems to automatically create the
> >> > AxInterop.VisOcx.dll file... and it is this file that is causing the > >> > problem
> >> > when i try to run the compiled exe.
> >> >
> >> >
> >> >
> >> > lee
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> > news:%2*****************@TK2MSFTNGP14.phx.gbl...
> >> >> DOH!
> >> >>
> >> >> I thought I saw just plain .ocx as the extension. Sorry.
> >> >>
> >> >> Now I have to try to find that control and see what I can come up
> >> >> with.
> >> >>
> >> >> --
> >> >> Gerry O'Brien
> >> >> Visual Basic.NET MVP
> >> >>
> >> >>
> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> news:ua**************@TK2MSFTNGP14.phx.gbl...
> >> >> > Hi Gerry,
> >> >> >
> >> >> > I have looked at the article and tried to run the tlbimp.exe on

the
> > ocx
> >> >> > file, however i get an error saying that the file is not a
> >> >> > valid
> >> >> > type
> >> >> > library.
> >> >> >
> >> >> > Lee
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> >> > news:uW**************@TK2MSFTNGP15.phx.gbl...
> >> >> >> I'm not able to find the ocx in the SDK and I'm not sure you will > > find
> >> >> >> and
> >> >> >> ActiveX control in the 2003 SDK anyway. Although there is a COM > > based
> >> >> >> object library that installs with the SDK, I cannot locate the
> > control
> >> >> >> you
> >> >> >> are referring to.
> >> >> >>
> >> >> >> I have yet to develop anything in .NET for Visio so I may not the > >> >> >> be
> >> > the
> >> >> >> best person to help here but I will try nonetheless.
> >> >> >>
> >> >> >> Here is a for a web site for you to take a look at. Althouth the > > site
> >> > is
> >> >> >> about C#, the code samples are in VB for this article.
> >> >> >>
> >> >> >> I think you may find part of your answer in the fact that you may > > not
> >> >> >> have
> >> >> >> run tlbimp.exe on the ocx file to apply a COM wrapper around it. > >> >> >>
> >> >> >> This article explains how to do just that and then how to isntall > >> >> >> it
> >> > into
> >> >> >> the GAC by using the sn.exe utility to create a strongly named
> >> > assembly.
> >> >> >>
> >> >> >>

http://www.csharpfriends.com/Article...x?articleID=43
> >> >> >>
> >> >> >> Hope it helps.
> >> >> >>
> >> >> >> Gerry
> >> >> >>
> >> >> >>
> >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> >> news:u%******************@TK2MSFTNGP10.phx.gbl...
> >> >> >> > Hi Gerry,
> >> >> >> >
> >> >> >> > It is referenced in the references section of the solution
> > explorer
> >> >> >> > (and
> >> >> > i
> >> >> >> > have referenced it in the coed by "import AxVisOcx =
> >> >> >> > AxMicrosoft.Office.Interop.VisOcx"
> >> >> >> >
> >> >> >> > After speaking with a work colleague we think the problem
> >> >> >> > may
> >> >> >> > have
> >> >> >> > something
> >> >> >> > to do witht he assembly not being in the GAC... when trying to > >> >> >> > add
> >> > this
> >> >> >> > assembly to the GAC i get an error message saying that it is

not
> >> >> > strongly
> >> >> >> > named.
> >> >> >> >
> >> >> >> > I believe that the assembly came with the Visio 2003 SDK.
> >> >> >> >
> >> >> >> > Unfortunately i do not have any more information. This is the > > first
> >> >> > time
> >> >> >> > i
> >> >> >> > have created an application using Visual Studio and the
> >> >> >> > first
> >> >> >> > time
> >> >> >> > using
> >> >> >
> >> >> >> > hte
> >> >> >> > Visio ActiveX control so it has got me a little stumped.
> >> >> >> >
> >> >> >> > Compiling and trying to run the program form the bin folder was > > the
> >> >> > first
> >> >> >> > thing i did (assuming that it would work). after that i

removed
> > the
> >> >> >> > reference, rebuilt, re-referenced and rebuilt.. still no luck. > >> >> >> >
> >> >> >> > Thanks for you help.
> >> >> >> >
> >> >> >> > regards
> >> >> >> >
> >> >> >> > Lee
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> >> >> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
> >> >> >> >> How is the AxInterop.VisOcx referenced? Are you certain it is > >> >> >> >> in
> >> > the
> >> >> >> >> correct location for the compiled version of your app?
> >> >> >> >>
> >> >> >> >> Do you include it in the setup of your app or have you just
> >> >> >> >> compiled
> >> >> > the
> >> >> >> >> project and attempted to run the exe from the bin folder?
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Gerry O'Brien
> >> >> >> >> Visual Basic.NET MVP
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> >> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
> >> >> >> >> > Hi,
> >> >> >> >> >
> >> >> >> >> > I have just written my first application using VB.NET.
> >> >> >> >> > The

app
> >> > works
> >> >> >> > fine
> >> >> >> >> > when i am running it within .NET for debugging purposes,
> > however
> >> >> >> >> > when
> >> >> > i
> >> >> >> >> > try
> >> >> >> >> > to run the app from the .exe file that .NET creates i get

the
> >> >> > following
> >> >> >> >> > error message:
> >> >> >> >> >
> >> >> >> >> > "An unhandled exception of type
> > 'System.IO.FileNotFoundException'
> >> >> >> > occurred
> >> >> >> >> > in VisioTimeline.exe
> >> >> >> >> >
> >> >> >> >> > Additional information: File or assembly name
> >> >> >> >> > AxInterop.VisOcx,
> >> >> >> >> > or
> >> >> > one
> >> >> >> > of
> >> >> >> >> > its dependencies, was not found."
> >> >> >> >> >
> >> >> >> >> > I have tried removing the AxInterop.VisOcx refernce from the > > app,
> >> >> >> >> > rebuilding
> >> >> >> >> > it then putting the reference back into the solution and
> >> > rebuilding
> >> >> > it
> >> >> >> >> > again
> >> >> >> >> > but i still get the same error.
> >> >> >> >> >
> >> >> >> >> > When the app tries to run and consequently debugs, the
> >> >> >> >> > disassembly
> >> >> >> >> > is
> >> >> >> >> > displayed but this is in machine code, which although i
> >> >> >> >> > touched
> >> >> >> >> > on
> >> >> >> >> > at
> >> >> >> > uni,
> >> >> >> >> > doesn't mean a thing to me.
> >> >> >> >> >
> >> >> >> >> > Can anyone help??
> >> >> >> >> >
> >> >> >> >> > Thanks for any and all help, it is greatly appreciated
> >> >> >> >> >
> >> >> >> >> > reagrds
> >> >> >> >> >
> >> >> >> >> > Lee
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>



Nov 21 '05 #12
Unfortunately it doesn't really solve the issue in that we can't justify
paying for a license for VS.NET just to run a singular program on a machine.

At this point i have totally run out of ideas, so much so that i may be
rasing a case with microsoft.

Thanks for your help Gerry.

regards

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:eQ**************@TK2MSFTNGP12.phx.gbl...
Interesting. I have never heard of that scenario before.

I hope it does solve your issue though.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Oh**************@tk2msftngp13.phx.gbl...
Hi Gerry,

I think i may have found the problem... it would appear that the app will only work if the other machine has VS.NET installed, it will not work in
the
VS.NET redistributable package is installed... this is a problem in itself because from my understanding we will need to get another license for ..NET to install it on the machine that my app needs to run on.

It also means that i am going to have to seperate the two modes of the
program so that the admin side cacn be used on our project managers
machines... this is not the ideal situation to be in and i can't for the
life of me understand why the app needs the full install of VS.NET to run.
I don't suppose you have any ideas why this might be the case?? or how to solve it?

If not then thank you very much for your help with this it is has been
very
appreciated.

regards

Lee


"Lee Newson" <le********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi Gerry,

I have checked all the files in the setup project and the
AxInterop.VisOcx.dll file is in it.
The app has two ways to run. Automatically create the timelines (no user interaction with the app) and the admin side where the user can define

what
timelines to create - which schedules to include from project server and various other settings.

When i run the auto mode it just falls over with the

system.io.filenotfound,
when i run it in admin mode i get the error (see attached txt file).

It would appear for whatever reason that the app cannot load the
AxInterop.VisOcx assembly.

I have also tried creating the project from scratch, adding the existing code files etc and using all the default VS.NET properties etc, still no luck. When i did this i had to drop the drawing control on the form

again,
and the AxInterop.VisOcx.dll file was created and i have not touched any
of
the settings for this.

The program runs absolutely fine on my machine the problem is still
deploying it to another machine (i used the setup wizard for this to

create
a setup project), all the files are included in this and are installed
to the other machine during setup.

Lee





"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:ep*************@TK2MSFTNGP10.phx.gbl...
> Just make sure that you have actually added that file in setup project so
> that it will be copied to the correct folder when the app is deployed
> on
> another machine. That is likely the problem you are having.
>
> --
> Gerry O'Brien
> Visual Basic.NET MVP
>
>
> "Lee Newson" <le********@hotmail.com> wrote in message
> news:OR*************@TK2MSFTNGP15.phx.gbl...
> > Yes, this file does get created in the bin folder, the problem
comes when
> > i
> > try to deply the app to a different machine which has the .NET
> > redistibutable package installed.
> >
> > I am wondering now if somehow i have to change the path to the file

from
> > f:\...\bin\AxInterop.VisOcx.dll to something else... but i am

unsure...
as
> > i
> > said initially this is the first time i have created either a windows app
> > or
> > programmed using the visio drawing control.
> >
> > Lee
> >
> >
> >
> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> > news:ur**************@tk2msftngp13.phx.gbl...
> >> Ok, again partly my own stupidity on this one. I was looking at

adding
a
> >> reference in the referece section manually.
> >>
> >> Instead, I added the control to the toolbox. Dropped it on the form and
> >> here is what is in my references section;
> >>
> >> AxVisOcx
> >> Visio
> >> VisOcx
> >>
> >> I'm not doing anything with the control at all, just placed it on
> >> the
> > form.
> >>
> >> Ran the app from the IDE, it opens and displays the Visio drawing
window.
> >>
> >> Compiled the app, ran the exe from the bin/debug folder, and all

works
> > well.
> >>
> >> I notice that the AxInterop.VisOcx.dll is in the bin/debug folder.

Is
> >> yours?
> >>
> >>
> >>
> >> --
> >> Gerry O'Brien
> >> Visual Basic.NET MVP
> >>
> >>
> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> news:Oh*************@TK2MSFTNGP15.phx.gbl...
> >> > Hi Gerry,
> >> >
> >> > I have just tried creating a basic form that only has the Visio
Drawing
> >> > control on it... to do this i added the component to the form

toolbox
> >> > (this
> >> > is the Microsoft.Office.Interop.VisOcx.dll type library) when i
> >> > add
the
> >> > drawing control to the form it seems to automatically create the
> >> > AxInterop.VisOcx.dll file... and it is this file that is causing

the
> >> > problem
> >> > when i try to run the compiled exe.
> >> >
> >> >
> >> >
> >> > lee
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> > news:%2*****************@TK2MSFTNGP14.phx.gbl...
> >> >> DOH!
> >> >>
> >> >> I thought I saw just plain .ocx as the extension. Sorry.
> >> >>
> >> >> Now I have to try to find that control and see what I can come up > >> >> with.
> >> >>
> >> >> --
> >> >> Gerry O'Brien
> >> >> Visual Basic.NET MVP
> >> >>
> >> >>
> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> news:ua**************@TK2MSFTNGP14.phx.gbl...
> >> >> > Hi Gerry,
> >> >> >
> >> >> > I have looked at the article and tried to run the tlbimp.exe on the
> > ocx
> >> >> > file, however i get an error saying that the file is not a
> >> >> > valid
> >> >> > type
> >> >> > library.
> >> >> >
> >> >> > Lee
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> >> > news:uW**************@TK2MSFTNGP15.phx.gbl...
> >> >> >> I'm not able to find the ocx in the SDK and I'm not sure you

will
> > find
> >> >> >> and
> >> >> >> ActiveX control in the 2003 SDK anyway. Although there is a

COM
> > based
> >> >> >> object library that installs with the SDK, I cannot locate the > > control
> >> >> >> you
> >> >> >> are referring to.
> >> >> >>
> >> >> >> I have yet to develop anything in .NET for Visio so I may not the
> >> >> >> be
> >> > the
> >> >> >> best person to help here but I will try nonetheless.
> >> >> >>
> >> >> >> Here is a for a web site for you to take a look at.
Althouth the
> > site
> >> > is
> >> >> >> about C#, the code samples are in VB for this article.
> >> >> >>
> >> >> >> I think you may find part of your answer in the fact that
you may
> > not
> >> >> >> have
> >> >> >> run tlbimp.exe on the ocx file to apply a COM wrapper around

it.
> >> >> >>
> >> >> >> This article explains how to do just that and then how to

isntall
> >> >> >> it
> >> > into
> >> >> >> the GAC by using the sn.exe utility to create a strongly
named > >> > assembly.
> >> >> >>
> >> >> >>
http://www.csharpfriends.com/Article...x?articleID=43
> >> >> >>
> >> >> >> Hope it helps.
> >> >> >>
> >> >> >> Gerry
> >> >> >>
> >> >> >>
> >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> >> news:u%******************@TK2MSFTNGP10.phx.gbl...
> >> >> >> > Hi Gerry,
> >> >> >> >
> >> >> >> > It is referenced in the references section of the solution
> > explorer
> >> >> >> > (and
> >> >> > i
> >> >> >> > have referenced it in the coed by "import AxVisOcx =
> >> >> >> > AxMicrosoft.Office.Interop.VisOcx"
> >> >> >> >
> >> >> >> > After speaking with a work colleague we think the problem
> >> >> >> > may
> >> >> >> > have
> >> >> >> > something
> >> >> >> > to do witht he assembly not being in the GAC... when trying to
> >> >> >> > add
> >> > this
> >> >> >> > assembly to the GAC i get an error message saying that it
is not
> >> >> > strongly
> >> >> >> > named.
> >> >> >> >
> >> >> >> > I believe that the assembly came with the Visio 2003 SDK.
> >> >> >> >
> >> >> >> > Unfortunately i do not have any more information. This is

the
> > first
> >> >> > time
> >> >> >> > i
> >> >> >> > have created an application using Visual Studio and the
> >> >> >> > first
> >> >> >> > time
> >> >> >> > using
> >> >> >
> >> >> >> > hte
> >> >> >> > Visio ActiveX control so it has got me a little stumped.
> >> >> >> >
> >> >> >> > Compiling and trying to run the program form the bin folder was
> > the
> >> >> > first
> >> >> >> > thing i did (assuming that it would work). after that i
removed
> > the
> >> >> >> > reference, rebuilt, re-referenced and rebuilt.. still no

luck.
> >> >> >> >
> >> >> >> > Thanks for you help.
> >> >> >> >
> >> >> >> > regards
> >> >> >> >
> >> >> >> > Lee
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
> >> >> >> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
> >> >> >> >> How is the AxInterop.VisOcx referenced? Are you certain
it is
> >> >> >> >> in
> >> > the
> >> >> >> >> correct location for the compiled version of your app?
> >> >> >> >>
> >> >> >> >> Do you include it in the setup of your app or have you
just > >> >> >> >> compiled
> >> >> > the
> >> >> >> >> project and attempted to run the exe from the bin folder?
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Gerry O'Brien
> >> >> >> >> Visual Basic.NET MVP
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
> >> >> >> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
> >> >> >> >> > Hi,
> >> >> >> >> >
> >> >> >> >> > I have just written my first application using VB.NET.
> >> >> >> >> > The
app
> >> > works
> >> >> >> > fine
> >> >> >> >> > when i am running it within .NET for debugging purposes, > > however
> >> >> >> >> > when
> >> >> > i
> >> >> >> >> > try
> >> >> >> >> > to run the app from the .exe file that .NET creates i get the
> >> >> > following
> >> >> >> >> > error message:
> >> >> >> >> >
> >> >> >> >> > "An unhandled exception of type
> > 'System.IO.FileNotFoundException'
> >> >> >> > occurred
> >> >> >> >> > in VisioTimeline.exe
> >> >> >> >> >
> >> >> >> >> > Additional information: File or assembly name
> >> >> >> >> > AxInterop.VisOcx,
> >> >> >> >> > or
> >> >> > one
> >> >> >> > of
> >> >> >> >> > its dependencies, was not found."
> >> >> >> >> >
> >> >> >> >> > I have tried removing the AxInterop.VisOcx refernce from the
> > app,
> >> >> >> >> > rebuilding
> >> >> >> >> > it then putting the reference back into the solution

and > >> > rebuilding
> >> >> > it
> >> >> >> >> > again
> >> >> >> >> > but i still get the same error.
> >> >> >> >> >
> >> >> >> >> > When the app tries to run and consequently debugs, the
> >> >> >> >> > disassembly
> >> >> >> >> > is
> >> >> >> >> > displayed but this is in machine code, which although i
> >> >> >> >> > touched
> >> >> >> >> > on
> >> >> >> >> > at
> >> >> >> > uni,
> >> >> >> >> > doesn't mean a thing to me.
> >> >> >> >> >
> >> >> >> >> > Can anyone help??
> >> >> >> >> >
> >> >> >> >> > Thanks for any and all help, it is greatly appreciated
> >> >> >> >> >
> >> >> >> >> > reagrds
> >> >> >> >> >
> >> >> >> >> > Lee
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>



Nov 21 '05 #13
Well, it doesn't make sense to have to install VS when the redistributable
provides the necessary run times.

Sorry I couldn't be of more help.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:OW**************@TK2MSFTNGP10.phx.gbl...
Unfortunately it doesn't really solve the issue in that we can't justify
paying for a license for VS.NET just to run a singular program on a
machine.

At this point i have totally run out of ideas, so much so that i may be
rasing a case with microsoft.

Thanks for your help Gerry.

regards

Lee

"Gerry O'Brien" <gk******@hotmail.com> wrote in message
news:eQ**************@TK2MSFTNGP12.phx.gbl...
Interesting. I have never heard of that scenario before.

I hope it does solve your issue though.

--
Gerry O'Brien
Visual Basic.NET MVP
"Lee Newson" <le********@hotmail.com> wrote in message
news:Oh**************@tk2msftngp13.phx.gbl...
> Hi Gerry,
>
> I think i may have found the problem... it would appear that the app will > only work if the other machine has VS.NET installed, it will not work
> in
> the
> VS.NET redistributable package is installed... this is a problem in itself > because from my understanding we will need to get another license for .NET > to install it on the machine that my app needs to run on.
>
> It also means that i am going to have to seperate the two modes of the
> program so that the admin side cacn be used on our project managers
> machines... this is not the ideal situation to be in and i can't for
> the
> life of me understand why the app needs the full install of VS.NET to run. >
> I don't suppose you have any ideas why this might be the case?? or how to > solve it?
>
> If not then thank you very much for your help with this it is has been
> very
> appreciated.
>
> regards
>
> Lee
>
>
>
>
> "Lee Newson" <le********@hotmail.com> wrote in message
> news:%2****************@TK2MSFTNGP09.phx.gbl...
>> Hi Gerry,
>>
>> I have checked all the files in the setup project and the
>> AxInterop.VisOcx.dll file is in it.
>> The app has two ways to run. Automatically create the timelines (no user >> interaction with the app) and the admin side where the user can define
> what
>> timelines to create - which schedules to include from project server and >> various other settings.
>>
>> When i run the auto mode it just falls over with the
> system.io.filenotfound,
>> when i run it in admin mode i get the error (see attached txt file).
>>
>> It would appear for whatever reason that the app cannot load the
>> AxInterop.VisOcx assembly.
>>
>> I have also tried creating the project from scratch, adding the existing >> code files etc and using all the default VS.NET properties etc, still no >> luck. When i did this i had to drop the drawing control on the form
> again,
>> and the AxInterop.VisOcx.dll file was created and i have not touched any > of
>> the settings for this.
>>
>> The program runs absolutely fine on my machine the problem is still
>> deploying it to another machine (i used the setup wizard for this to
> create
>> a setup project), all the files are included in this and are installed to >> the other machine during setup.
>>
>> Lee
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> news:ep*************@TK2MSFTNGP10.phx.gbl...
>> > Just make sure that you have actually added that file in setup project > so
>> > that it will be copied to the correct folder when the app is
>> > deployed
>> > on
>> > another machine. That is likely the problem you are having.
>> >
>> > --
>> > Gerry O'Brien
>> > Visual Basic.NET MVP
>> >
>> >
>> > "Lee Newson" <le********@hotmail.com> wrote in message
>> > news:OR*************@TK2MSFTNGP15.phx.gbl...
>> > > Yes, this file does get created in the bin folder, the problem comes >> when
>> > > i
>> > > try to deply the app to a different machine which has the .NET
>> > > redistibutable package installed.
>> > >
>> > > I am wondering now if somehow i have to change the path to the
>> > > file
> from
>> > > f:\...\bin\AxInterop.VisOcx.dll to something else... but i am
> unsure...
>> as
>> > > i
>> > > said initially this is the first time i have created either a windows >> app
>> > > or
>> > > programmed using the visio drawing control.
>> > >
>> > > Lee
>> > >
>> > >
>> > >
>> > > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > > news:ur**************@tk2msftngp13.phx.gbl...
>> > >> Ok, again partly my own stupidity on this one. I was looking at
> adding
>> a
>> > >> reference in the referece section manually.
>> > >>
>> > >> Instead, I added the control to the toolbox. Dropped it on the form >> and
>> > >> here is what is in my references section;
>> > >>
>> > >> AxVisOcx
>> > >> Visio
>> > >> VisOcx
>> > >>
>> > >> I'm not doing anything with the control at all, just placed it on
>> > >> the
>> > > form.
>> > >>
>> > >> Ran the app from the IDE, it opens and displays the Visio drawing
>> window.
>> > >>
>> > >> Compiled the app, ran the exe from the bin/debug folder, and all
> works
>> > > well.
>> > >>
>> > >> I notice that the AxInterop.VisOcx.dll is in the bin/debug
>> > >> folder.
> Is
>> > >> yours?
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Gerry O'Brien
>> > >> Visual Basic.NET MVP
>> > >>
>> > >>
>> > >> "Lee Newson" <le********@hotmail.com> wrote in message
>> > >> news:Oh*************@TK2MSFTNGP15.phx.gbl...
>> > >> > Hi Gerry,
>> > >> >
>> > >> > I have just tried creating a basic form that only has the Visio
>> Drawing
>> > >> > control on it... to do this i added the component to the form
> toolbox
>> > >> > (this
>> > >> > is the Microsoft.Office.Interop.VisOcx.dll type library) when i
>> > >> > add
>> the
>> > >> > drawing control to the form it seems to automatically create
>> > >> > the
>> > >> > AxInterop.VisOcx.dll file... and it is this file that is
>> > >> > causing
> the
>> > >> > problem
>> > >> > when i try to run the compiled exe.
>> > >> >
>> > >> >
>> > >> >
>> > >> > lee
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > >> > news:%2*****************@TK2MSFTNGP14.phx.gbl...
>> > >> >> DOH!
>> > >> >>
>> > >> >> I thought I saw just plain .ocx as the extension. Sorry.
>> > >> >>
>> > >> >> Now I have to try to find that control and see what I can come up >> > >> >> with.
>> > >> >>
>> > >> >> --
>> > >> >> Gerry O'Brien
>> > >> >> Visual Basic.NET MVP
>> > >> >>
>> > >> >>
>> > >> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> > >> >> news:ua**************@TK2MSFTNGP14.phx.gbl...
>> > >> >> > Hi Gerry,
>> > >> >> >
>> > >> >> > I have looked at the article and tried to run the tlbimp.exe on >> the
>> > > ocx
>> > >> >> > file, however i get an error saying that the file is not a
>> > >> >> > valid
>> > >> >> > type
>> > >> >> > library.
>> > >> >> >
>> > >> >> > Lee
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > >> >> > news:uW**************@TK2MSFTNGP15.phx.gbl...
>> > >> >> >> I'm not able to find the ocx in the SDK and I'm not sure
>> > >> >> >> you
> will
>> > > find
>> > >> >> >> and
>> > >> >> >> ActiveX control in the 2003 SDK anyway. Although there is
>> > >> >> >> a
> COM
>> > > based
>> > >> >> >> object library that installs with the SDK, I cannot locate the >> > > control
>> > >> >> >> you
>> > >> >> >> are referring to.
>> > >> >> >>
>> > >> >> >> I have yet to develop anything in .NET for Visio so I may not > the
>> > >> >> >> be
>> > >> > the
>> > >> >> >> best person to help here but I will try nonetheless.
>> > >> >> >>
>> > >> >> >> Here is a for a web site for you to take a look at. Althouth > the
>> > > site
>> > >> > is
>> > >> >> >> about C#, the code samples are in VB for this article.
>> > >> >> >>
>> > >> >> >> I think you may find part of your answer in the fact that you > may
>> > > not
>> > >> >> >> have
>> > >> >> >> run tlbimp.exe on the ocx file to apply a COM wrapper
>> > >> >> >> around
> it.
>> > >> >> >>
>> > >> >> >> This article explains how to do just that and then how to
> isntall
>> > >> >> >> it
>> > >> > into
>> > >> >> >> the GAC by using the sn.exe utility to create a strongly named >> > >> > assembly.
>> > >> >> >>
>> > >> >> >>
>> http://www.csharpfriends.com/Article...x?articleID=43
>> > >> >> >>
>> > >> >> >> Hope it helps.
>> > >> >> >>
>> > >> >> >> Gerry
>> > >> >> >>
>> > >> >> >>
>> > >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> > >> >> >> news:u%******************@TK2MSFTNGP10.phx.gbl...
>> > >> >> >> > Hi Gerry,
>> > >> >> >> >
>> > >> >> >> > It is referenced in the references section of the
>> > >> >> >> > solution
>> > > explorer
>> > >> >> >> > (and
>> > >> >> > i
>> > >> >> >> > have referenced it in the coed by "import AxVisOcx =
>> > >> >> >> > AxMicrosoft.Office.Interop.VisOcx"
>> > >> >> >> >
>> > >> >> >> > After speaking with a work colleague we think the problem
>> > >> >> >> > may
>> > >> >> >> > have
>> > >> >> >> > something
>> > >> >> >> > to do witht he assembly not being in the GAC... when trying > to
>> > >> >> >> > add
>> > >> > this
>> > >> >> >> > assembly to the GAC i get an error message saying that it is >> not
>> > >> >> > strongly
>> > >> >> >> > named.
>> > >> >> >> >
>> > >> >> >> > I believe that the assembly came with the Visio 2003 SDK.
>> > >> >> >> >
>> > >> >> >> > Unfortunately i do not have any more information. This
>> > >> >> >> > is
> the
>> > > first
>> > >> >> > time
>> > >> >> >> > i
>> > >> >> >> > have created an application using Visual Studio and the
>> > >> >> >> > first
>> > >> >> >> > time
>> > >> >> >> > using
>> > >> >> >
>> > >> >> >> > hte
>> > >> >> >> > Visio ActiveX control so it has got me a little stumped.
>> > >> >> >> >
>> > >> >> >> > Compiling and trying to run the program form the bin folder > was
>> > > the
>> > >> >> > first
>> > >> >> >> > thing i did (assuming that it would work). after that i
>> removed
>> > > the
>> > >> >> >> > reference, rebuilt, re-referenced and rebuilt.. still no
> luck.
>> > >> >> >> >
>> > >> >> >> > Thanks for you help.
>> > >> >> >> >
>> > >> >> >> > regards
>> > >> >> >> >
>> > >> >> >> > Lee
>> > >> >> >> >
>> > >> >> >> >
>> > >> >> >> >
>> > >> >> >> > "Gerry O'Brien" <gk******@hotmail.com> wrote in message
>> > >> >> >> > news:Oz**************@TK2MSFTNGP10.phx.gbl...
>> > >> >> >> >> How is the AxInterop.VisOcx referenced? Are you certain it > is
>> > >> >> >> >> in
>> > >> > the
>> > >> >> >> >> correct location for the compiled version of your app?
>> > >> >> >> >>
>> > >> >> >> >> Do you include it in the setup of your app or have you just >> > >> >> >> >> compiled
>> > >> >> > the
>> > >> >> >> >> project and attempted to run the exe from the bin
>> > >> >> >> >> folder?
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >> >> --
>> > >> >> >> >> Gerry O'Brien
>> > >> >> >> >> Visual Basic.NET MVP
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >> >> "Lee Newson" <le********@hotmail.com> wrote in message
>> > >> >> >> >> news:Or**************@TK2MSFTNGP14.phx.gbl...
>> > >> >> >> >> > Hi,
>> > >> >> >> >> >
>> > >> >> >> >> > I have just written my first application using VB.NET.
>> > >> >> >> >> > The
>> app
>> > >> > works
>> > >> >> >> > fine
>> > >> >> >> >> > when i am running it within .NET for debugging purposes, >> > > however
>> > >> >> >> >> > when
>> > >> >> > i
>> > >> >> >> >> > try
>> > >> >> >> >> > to run the app from the .exe file that .NET creates i get >> the
>> > >> >> > following
>> > >> >> >> >> > error message:
>> > >> >> >> >> >
>> > >> >> >> >> > "An unhandled exception of type
>> > > 'System.IO.FileNotFoundException'
>> > >> >> >> > occurred
>> > >> >> >> >> > in VisioTimeline.exe
>> > >> >> >> >> >
>> > >> >> >> >> > Additional information: File or assembly name
>> > >> >> >> >> > AxInterop.VisOcx,
>> > >> >> >> >> > or
>> > >> >> > one
>> > >> >> >> > of
>> > >> >> >> >> > its dependencies, was not found."
>> > >> >> >> >> >
>> > >> >> >> >> > I have tried removing the AxInterop.VisOcx refernce from > the
>> > > app,
>> > >> >> >> >> > rebuilding
>> > >> >> >> >> > it then putting the reference back into the solution and >> > >> > rebuilding
>> > >> >> > it
>> > >> >> >> >> > again
>> > >> >> >> >> > but i still get the same error.
>> > >> >> >> >> >
>> > >> >> >> >> > When the app tries to run and consequently debugs, the
>> > >> >> >> >> > disassembly
>> > >> >> >> >> > is
>> > >> >> >> >> > displayed but this is in machine code, which although
>> > >> >> >> >> > i
>> > >> >> >> >> > touched
>> > >> >> >> >> > on
>> > >> >> >> >> > at
>> > >> >> >> > uni,
>> > >> >> >> >> > doesn't mean a thing to me.
>> > >> >> >> >> >
>> > >> >> >> >> > Can anyone help??
>> > >> >> >> >> >
>> > >> >> >> >> > Thanks for any and all help, it is greatly appreciated
>> > >> >> >> >> >
>> > >> >> >> >> > reagrds
>> > >> >> >> >> >
>> > >> >> >> >> > Lee
>> > >> >> >> >> >
>> > >> >> >> >> >
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >> >
>> > >> >> >> >
>> > >> >> >>
>> > >> >> >>
>> > >> >> >
>> > >> >> >
>> > >> >>
>> > >> >>
>> > >> >
>> > >> >
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>>
>>
>>
>
>



Nov 21 '05 #14

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Tim Haughton | last post: by
6 posts views Thread by Ayende Rahien | last post: by
1 post views Thread by Günther Rühmann | last post: by
21 posts views Thread by Dan Tallent | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.