| Groups | Blog | Home |
dotnet general : Potential bug?
Hi,
Can somebody try this? Make a new .NET class library with one class. Create a method that simply instantiates an instance of ADODB.Connection. You will need to reference the ADODB assembly under .NET tab. Build the project. Now make a vbscript file that creates an object of the class you have just built. Then call the public method (which will attempt to instantiate the ADODB.connection). If you have added a strong key and registered the type library, and placed the assembly in the global assembly cache all works fine. However, try moving the assembly to a computer without visual studio (with a setup project) and see how you go. I get a "File or Assembly name ADODB, or one of its dependencies was not found". How bout you?
Hi Nick,
I have. First 2.6, 2.6 and now 2.8. Did you try it and if so did it work? Jesse [quoted text, click to view] "Nick Malik [Microsoft]" wrote:
> install MDAC on the target computer > > -- > --- Nick Malik [Microsoft] > MCSD, CFPS, Certified Scrummaster > http://blogs.msdn.com/nickmalik > > Disclaimer: Opinions expressed in this forum are my own, and not > representative of my employer. > I do not answer questions on behalf of my employer. I'm just a > programmer helping programmers. > -- > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > news:77885FB6-3DD2-41D8-8725-1047C297F32B@microsoft.com... > > Hi, > > > > Can somebody try this? Make a new .NET class library with one class. > > Create a method that simply instantiates an instance of ADODB.Connection. > > You will need to reference the ADODB assembly under .NET tab. Build the > > project. Now make a vbscript file that creates an object of the class you > > have just built. Then call the public method (which will attempt to > > instantiate the ADODB.connection). If you have added a strong key and > > registered the type library, and placed the assembly in the global > assembly > > cache all works fine. However, try moving the assembly to a computer > without > > visual studio (with a setup project) and see how you go. > > > > I get a "File or Assembly name ADODB, or one of its dependencies was not > > found". How bout you? > > Jesse > >
install MDAC on the target computer
-- --- Nick Malik [Microsoft] MCSD, CFPS, Certified Scrummaster http://blogs.msdn.com/nickmalik Disclaimer: Opinions expressed in this forum are my own, and not representative of my employer. I do not answer questions on behalf of my employer. I'm just a programmer helping programmers. -- [quoted text, click to view] "Jessard" <Jessard@discussions.microsoft.com> wrote in message news:77885FB6-3DD2-41D8-8725-1047C297F32B@microsoft.com... > Hi, > > Can somebody try this? Make a new .NET class library with one class. > Create a method that simply instantiates an instance of ADODB.Connection. > You will need to reference the ADODB assembly under .NET tab. Build the > project. Now make a vbscript file that creates an object of the class you > have just built. Then call the public method (which will attempt to > instantiate the ADODB.connection). If you have added a strong key and > registered the type library, and placed the assembly in the global assembly > cache all works fine. However, try moving the assembly to a computer without > visual studio (with a setup project) and see how you go. > > I get a "File or Assembly name ADODB, or one of its dependencies was not > found". How bout you? > Jesse
I've directly coded, or supervised, two dozen different projects that use
database connectivity. Never had the error you are discussing. Tell me about the systems that you are using. What is the configuration of your dev machine? your target machine? (Especially your target machine: do you have any service packs installed? Were there errors when installing the framework?) Have you taking your target app and installed it anywhere else? If so, does it fail there? If so, describe the config of that machine as well. -- --- Nick Malik [Microsoft] MCSD, CFPS, Certified Scrummaster http://blogs.msdn.com/nickmalik Disclaimer: Opinions expressed in this forum are my own, and not representative of my employer. I do not answer questions on behalf of my employer. I'm just a programmer helping programmers. -- [quoted text, click to view] "Jessard" <Jessard@discussions.microsoft.com> wrote in message news:C3DA1B63-A90D-4D04-AA96-72FC94FDE7B3@microsoft.com... > Hi Nick, > > I have. First 2.6, 2.6 and now 2.8. > > Did you try it and if so did it work? > > Jesse > > "Nick Malik [Microsoft]" wrote: > > > install MDAC on the target computer > > > > -- > > --- Nick Malik [Microsoft] > > MCSD, CFPS, Certified Scrummaster > > http://blogs.msdn.com/nickmalik > > > > Disclaimer: Opinions expressed in this forum are my own, and not > > representative of my employer. > > I do not answer questions on behalf of my employer. I'm just a > > programmer helping programmers. > > -- > > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > > news:77885FB6-3DD2-41D8-8725-1047C297F32B@microsoft.com... > > > Hi, > > > > > > Can somebody try this? Make a new .NET class library with one class. > > > Create a method that simply instantiates an instance of ADODB.Connection. > > > You will need to reference the ADODB assembly under .NET tab. Build the > > > project. Now make a vbscript file that creates an object of the class you > > > have just built. Then call the public method (which will attempt to > > > instantiate the ADODB.connection). If you have added a strong key and > > > registered the type library, and placed the assembly in the global > > assembly > > > cache all works fine. However, try moving the assembly to a computer > > without > > > visual studio (with a setup project) and see how you go. > > > > > > I get a "File or Assembly name ADODB, or one of its dependencies was not > > > found". How bout you? > > > Jesse > > > > > >
The development machine has VS.NET 2003. It is running Windows 2000 with
SP4. I have MDAC 7.1 on it. The target machine is a Windows 2000 Server with SP4 also. This originally had MDAC 2.6, so I tried it with 2.7 and now 2.8 - No luck. There were no problems installing the .NET Redistributable Package on it. I have also got my brother to try it on his Windows XP Pro machine which was a new installation so was likely to have any recent service packs. In addition to installing the .NET framework on his computer, I got him to install the SDK from the microsoft website - no go. On both target machines, it is fine if the class is being called by a .NET app but not when being called from VBscript with something like: Dim conn Set conn = CreateObject("MyAssembly.MyClass") conn.method It actually fails on the third line, indicating that object is created but when the method is called the ADODB.Connection object cannot be instantiated. I urge you to try one more time, I think you will be surprised to find that it will not work. Obviously, it CAN work, as it does on the development machine. By the way, Thanks for taking an interest. and Merry Christmas [quoted text, click to view] "Nick Malik [Microsoft]" wrote:
> I've directly coded, or supervised, two dozen different projects that use > database connectivity. Never had the error you are discussing. > > Tell me about the systems that you are using. What is the configuration of > your dev machine? your target machine? > > (Especially your target machine: do you have any service packs installed? > Were there errors when installing the framework?) > > Have you taking your target app and installed it anywhere else? If so, does > it fail there? If so, describe the config of that machine as well. > > -- > --- Nick Malik [Microsoft] > MCSD, CFPS, Certified Scrummaster > http://blogs.msdn.com/nickmalik > > Disclaimer: Opinions expressed in this forum are my own, and not > representative of my employer. > I do not answer questions on behalf of my employer. I'm just a > programmer helping programmers. > -- > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > news:C3DA1B63-A90D-4D04-AA96-72FC94FDE7B3@microsoft.com... > > Hi Nick, > > > > I have. First 2.6, 2.6 and now 2.8. > > > > Did you try it and if so did it work? > > > > Jesse > > > > "Nick Malik [Microsoft]" wrote: > > > > > install MDAC on the target computer > > > > > > -- > > > --- Nick Malik [Microsoft] > > > MCSD, CFPS, Certified Scrummaster > > > http://blogs.msdn.com/nickmalik > > > > > > Disclaimer: Opinions expressed in this forum are my own, and not > > > representative of my employer. > > > I do not answer questions on behalf of my employer. I'm just a > > > programmer helping programmers. > > > -- > > > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > > > news:77885FB6-3DD2-41D8-8725-1047C297F32B@microsoft.com... > > > > Hi, > > > > > > > > Can somebody try this? Make a new .NET class library with one class. > > > > Create a method that simply instantiates an instance of > ADODB.Connection. > > > > You will need to reference the ADODB assembly under .NET tab. Build > the > > > > project. Now make a vbscript file that creates an object of the class > you > > > > have just built. Then call the public method (which will attempt to > > > > instantiate the ADODB.connection). If you have added a strong key and > > > > registered the type library, and placed the assembly in the global > > > assembly > > > > cache all works fine. However, try moving the assembly to a computer > > > without > > > > visual studio (with a setup project) and see how you go. > > > > > > > > I get a "File or Assembly name ADODB, or one of its dependencies was > not > > > > found". How bout you? > > > > Jesse > > > > > > > > > > >
OK. I got more info that time. I think I get the idea.
You are running your object from Windows Script Host, right? What version of WSH are you running on the target environment? [Normally, WSH 2.0 ships on Win2K. The current version is WSH 5.6. You can download the newest version from: http://msdn.microsoft.com/scripting ] -- --- Nick Malik [Microsoft] MCSD, CFPS, Certified Scrummaster http://blogs.msdn.com/nickmalik Disclaimer: Opinions expressed in this forum are my own, and not representative of my employer. I do not answer questions on behalf of my employer. I'm just a programmer helping programmers. -- [quoted text, click to view] "Jessard" <Jessard@discussions.microsoft.com> wrote in message news:83F91A1D-B7FD-4A61-83B5-CD29A182CBDF@microsoft.com... > The development machine has VS.NET 2003. It is running Windows 2000 with > SP4. I have MDAC 7.1 on it. The target machine is a Windows 2000 Server > with SP4 also. This originally had MDAC 2.6, so I tried it with 2.7 and now > 2.8 - No luck. There were no problems installing the .NET Redistributable > Package on it. I have also got my brother to try it on his Windows XP Pro > machine which was a new installation so was likely to have any recent service > packs. In addition to installing the .NET framework on his computer, I got > him to install the SDK from the microsoft website - no go. On both target > machines, it is fine if the class is being called by a .NET app but not when > being called from VBscript with something like: > > Dim conn > Set conn = CreateObject("MyAssembly.MyClass") > conn.method > > It actually fails on the third line, indicating that object is created but > when the method is called the ADODB.Connection object cannot be instantiated. > > I urge you to try one more time, I think you will be surprised to find that > it will not work. Obviously, it CAN work, as it does on the development > machine. > > By the way, > Thanks for taking an interest. > and > Merry Christmas > > > > "Nick Malik [Microsoft]" wrote: > > > I've directly coded, or supervised, two dozen different projects that use > > database connectivity. Never had the error you are discussing. > > > > Tell me about the systems that you are using. What is the configuration of > > your dev machine? your target machine? > > > > (Especially your target machine: do you have any service packs installed? > > Were there errors when installing the framework?) > > > > Have you taking your target app and installed it anywhere else? If so, does > > it fail there? If so, describe the config of that machine as well. > > > > -- > > --- Nick Malik [Microsoft] > > MCSD, CFPS, Certified Scrummaster > > http://blogs.msdn.com/nickmalik > > > > Disclaimer: Opinions expressed in this forum are my own, and not > > representative of my employer. > > I do not answer questions on behalf of my employer. I'm just a > > programmer helping programmers. > > -- > > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > > news:C3DA1B63-A90D-4D04-AA96-72FC94FDE7B3@microsoft.com... > > > Hi Nick, > > > > > > I have. First 2.6, 2.6 and now 2.8. > > > > > > Did you try it and if so did it work? > > > > > > Jesse > > > > > > "Nick Malik [Microsoft]" wrote: > > > > > > > install MDAC on the target computer > > > > > > > > -- > > > > --- Nick Malik [Microsoft] > > > > MCSD, CFPS, Certified Scrummaster > > > > http://blogs.msdn.com/nickmalik > > > > > > > > Disclaimer: Opinions expressed in this forum are my own, and not > > > > representative of my employer. > > > > I do not answer questions on behalf of my employer. I'm just a > > > > programmer helping programmers. > > > > -- > > > > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > > > > news:77885FB6-3DD2-41D8-8725-1047C297F32B@microsoft.com... > > > > > Hi, > > > > > > > > > > Can somebody try this? Make a new .NET class library with one class. > > > > > Create a method that simply instantiates an instance of > > ADODB.Connection. > > > > > You will need to reference the ADODB assembly under .NET tab. Build > > the > > > > > project. Now make a vbscript file that creates an object of the class > > you > > > > > have just built. Then call the public method (which will attempt to > > > > > instantiate the ADODB.connection). If you have added a strong key and > > > > > registered the type library, and placed the assembly in the global > > > > assembly > > > > > cache all works fine. However, try moving the assembly to a computer > > > > without > > > > > visual studio (with a setup project) and see how you go. > > > > > > > > > > I get a "File or Assembly name ADODB, or one of its dependencies was > > not > > > > > found". How bout you? > > > > > Jesse > > > > > > > > > > > > > > > > > >
Yes, I beleive vbscript uses Windows Script Host, however I'm not 100% sure.
I installed the update for this as you suggested on my brothers XP machine and also service pack 2. Still the same error. Any other ideas? [quoted text, click to view] "Nick Malik [Microsoft]" wrote:
> OK. I got more info that time. I think I get the idea. > > You are running your object from Windows Script Host, right? > > What version of WSH are you running on the target environment? > [Normally, WSH 2.0 ships on Win2K. The current version is WSH 5.6. You can > download the newest version from: > http://msdn.microsoft.com/scripting ] > > -- > --- Nick Malik [Microsoft] > MCSD, CFPS, Certified Scrummaster > http://blogs.msdn.com/nickmalik > > Disclaimer: Opinions expressed in this forum are my own, and not > representative of my employer. > I do not answer questions on behalf of my employer. I'm just a > programmer helping programmers. > -- > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > news:83F91A1D-B7FD-4A61-83B5-CD29A182CBDF@microsoft.com... > > The development machine has VS.NET 2003. It is running Windows 2000 with > > SP4. I have MDAC 7.1 on it. The target machine is a Windows 2000 Server > > with SP4 also. This originally had MDAC 2.6, so I tried it with 2.7 and > now > > 2.8 - No luck. There were no problems installing the .NET Redistributable > > Package on it. I have also got my brother to try it on his Windows XP Pro > > machine which was a new installation so was likely to have any recent > service > > packs. In addition to installing the .NET framework on his computer, I > got > > him to install the SDK from the microsoft website - no go. On both target > > machines, it is fine if the class is being called by a .NET app but not > when > > being called from VBscript with something like: > > > > Dim conn > > Set conn = CreateObject("MyAssembly.MyClass") > > conn.method > > > > It actually fails on the third line, indicating that object is created but > > when the method is called the ADODB.Connection object cannot be > instantiated. > > > > I urge you to try one more time, I think you will be surprised to find > that > > it will not work. Obviously, it CAN work, as it does on the development > > machine. > > > > By the way, > > Thanks for taking an interest. > > and > > Merry Christmas > > > > > > > > "Nick Malik [Microsoft]" wrote: > > > > > I've directly coded, or supervised, two dozen different projects that > use > > > database connectivity. Never had the error you are discussing. > > > > > > Tell me about the systems that you are using. What is the configuration > of > > > your dev machine? your target machine? > > > > > > (Especially your target machine: do you have any service packs > installed? > > > Were there errors when installing the framework?) > > > > > > Have you taking your target app and installed it anywhere else? If so, > does > > > it fail there? If so, describe the config of that machine as well. > > > > > > -- > > > --- Nick Malik [Microsoft] > > > MCSD, CFPS, Certified Scrummaster > > > http://blogs.msdn.com/nickmalik > > > > > > Disclaimer: Opinions expressed in this forum are my own, and not > > > representative of my employer. > > > I do not answer questions on behalf of my employer. I'm just a > > > programmer helping programmers. > > > -- > > > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > > > news:C3DA1B63-A90D-4D04-AA96-72FC94FDE7B3@microsoft.com... > > > > Hi Nick, > > > > > > > > I have. First 2.6, 2.6 and now 2.8. > > > > > > > > Did you try it and if so did it work? > > > > > > > > Jesse > > > > > > > > "Nick Malik [Microsoft]" wrote: > > > > > > > > > install MDAC on the target computer > > > > > > > > > > -- > > > > > --- Nick Malik [Microsoft] > > > > > MCSD, CFPS, Certified Scrummaster > > > > > http://blogs.msdn.com/nickmalik > > > > > > > > > > Disclaimer: Opinions expressed in this forum are my own, and not > > > > > representative of my employer. > > > > > I do not answer questions on behalf of my employer. I'm just a > > > > > programmer helping programmers. > > > > > -- > > > > > "Jessard" <Jessard@discussions.microsoft.com> wrote in message > > > > > news:77885FB6-3DD2-41D8-8725-1047C297F32B@microsoft.com... > > > > > > Hi, > > > > > > > > > > > > Can somebody try this? Make a new .NET class library with one > class. > > > > > > Create a method that simply instantiates an instance of > > > ADODB.Connection. > > > > > > You will need to reference the ADODB assembly under .NET tab. > Build > > > the > > > > > > project. Now make a vbscript file that creates an object of the > class > > > you > > > > > > have just built. Then call the public method (which will attempt > to > > > > > > instantiate the ADODB.connection). If you have added a strong key > and > > > > > > registered the type library, and placed the assembly in the global > > > > > assembly > > > > > > cache all works fine. However, try moving the assembly to a > computer > > > > > without > > > > > > visual studio (with a setup project) and see how you go. > > > > > > > > > > > > I get a "File or Assembly name ADODB, or one of its dependencies > was > > > not > > > > > > found". How bout you? > > > > > > Jesse > > > > > > > > > > > > > > > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |