iAnywhere.Data.AsaClient
-
hi all, i have a small doubt, which kicking me back to somewhere. i am using and used lot of custom dlls on my projects which i will be transport with .exe file on delivery time. Now, i am using Sybase database in one of my project. Here i am using Managed provider for Sybase data accessing. iAnywhere.Data.AsaClient is the name of managed provider which use to access Sybase database. When i try to export and try to install my application on some other machine , it is installing properly and i can see iAnywhere.Data.AsaClient is also exported with my .exe file. Here the problem start, when i start running the application, it is not connecting to the Sybase database even though iAnywhere.Data.AsaClient is available . If i want to run my application, i need to install Sybase (Only the provider) in that machine. I think my application is not referring IAnywhere.Data.Client from its installed directory. And application is working fine, if i install iAnywhere.Data.AsaClient in GAC where i installed my application. But this will won't serve my purpose. And i can't rely on users or implementation people to get it done. Any idea which will help me to get out of this Sybase installation will be most appreciated.;) Sreejith Nair [ My Articles ]
-
hi all, i have a small doubt, which kicking me back to somewhere. i am using and used lot of custom dlls on my projects which i will be transport with .exe file on delivery time. Now, i am using Sybase database in one of my project. Here i am using Managed provider for Sybase data accessing. iAnywhere.Data.AsaClient is the name of managed provider which use to access Sybase database. When i try to export and try to install my application on some other machine , it is installing properly and i can see iAnywhere.Data.AsaClient is also exported with my .exe file. Here the problem start, when i start running the application, it is not connecting to the Sybase database even though iAnywhere.Data.AsaClient is available . If i want to run my application, i need to install Sybase (Only the provider) in that machine. I think my application is not referring IAnywhere.Data.Client from its installed directory. And application is working fine, if i install iAnywhere.Data.AsaClient in GAC where i installed my application. But this will won't serve my purpose. And i can't rely on users or implementation people to get it done. Any idea which will help me to get out of this Sybase installation will be most appreciated.;) Sreejith Nair [ My Articles ]
Is the DLL in the application directory, or one of its subdirectories? If it's not, then the CLR has no way of knowing where it is, unless you point it to a specific location in the configuration file. Because the GAC is a standard location known to the CLR, it'll be able to pick DLL's loaded there by itself. Regards Senthil _____________________________ My Blog | My Articles | WinMacro
-
Is the DLL in the application directory, or one of its subdirectories? If it's not, then the CLR has no way of knowing where it is, unless you point it to a specific location in the configuration file. Because the GAC is a standard location known to the CLR, it'll be able to pick DLL's loaded there by itself. Regards Senthil _____________________________ My Blog | My Articles | WinMacro
Yes, Dll is in the application directory. You wrote: Because the GAC is a standard location known to the CLR, it'll be able to pick DLL's loaded there by itself. I am not talking abt or least bothered abt GAC. I just wrote to inform the thread submitters that , i don't want to play with GAC. To be simple, i can't able to tell the user or Implimentation guys to try with GAC. What i need is, it need to work IAnywhere.Data.AsaClient like other custom dlls, which we using some or all applications. Any Idea ?:-D Sreejith Nair [ My Articles ]
-
hi all, i have a small doubt, which kicking me back to somewhere. i am using and used lot of custom dlls on my projects which i will be transport with .exe file on delivery time. Now, i am using Sybase database in one of my project. Here i am using Managed provider for Sybase data accessing. iAnywhere.Data.AsaClient is the name of managed provider which use to access Sybase database. When i try to export and try to install my application on some other machine , it is installing properly and i can see iAnywhere.Data.AsaClient is also exported with my .exe file. Here the problem start, when i start running the application, it is not connecting to the Sybase database even though iAnywhere.Data.AsaClient is available . If i want to run my application, i need to install Sybase (Only the provider) in that machine. I think my application is not referring IAnywhere.Data.Client from its installed directory. And application is working fine, if i install iAnywhere.Data.AsaClient in GAC where i installed my application. But this will won't serve my purpose. And i can't rely on users or implementation people to get it done. Any idea which will help me to get out of this Sybase installation will be most appreciated.;) Sreejith Nair [ My Articles ]
It is not connecting? Whats the error message? What kind of exception is raised? Where is it raised? The only hint I can give you without any futher info is, that you should check that not only the 'iAnywhere.Data.AsaClient.dll' is present but also 'dbdata9.dll', which is also needed.
-
It is not connecting? Whats the error message? What kind of exception is raised? Where is it raised? The only hint I can give you without any futher info is, that you should check that not only the 'iAnywhere.Data.AsaClient.dll' is present but also 'dbdata9.dll', which is also needed.
Little more clear please... I am getting an error message says, Unable to connect to Ianywhere.Data.Asaclient. The moment i install Sybase to that computer, my application won't show any error message and will work smoothly. Anyhow what is that 'dbdata9.dll'. Where i will get this ? What is the realt use of that file ? What is the important of that .dll in my application ? Give me some more idea .:cool: Sreejith Nair [ My Articles ]
-
Little more clear please... I am getting an error message says, Unable to connect to Ianywhere.Data.Asaclient. The moment i install Sybase to that computer, my application won't show any error message and will work smoothly. Anyhow what is that 'dbdata9.dll'. Where i will get this ? What is the realt use of that file ? What is the important of that .dll in my application ? Give me some more idea .:cool: Sreejith Nair [ My Articles ]
Have a look at Adaptive Server Anywhere .NET data provider required files. It seems to just be a helper library. Find it, check wether it needs com registration and put it into the application directory.
-
Have a look at Adaptive Server Anywhere .NET data provider required files. It seems to just be a helper library. Find it, check wether it needs com registration and put it into the application directory.
Let me try that first. anyhow thanks a lot for u'r support.:-D Sreejith Nair [ My Articles ]
-
Have a look at Adaptive Server Anywhere .NET data provider required files. It seems to just be a helper library. Find it, check wether it needs com registration and put it into the application directory.
I tried the way you told. But i can't convert that dbdata8.dll valid assembly. The error which i am getting is , it is not a valid library or Com. Please help to come out from this issue.:( Sreejith Nair [ My Articles ]
-
I tried the way you told. But i can't convert that dbdata8.dll valid assembly. The error which i am getting is , it is not a valid library or Com. Please help to come out from this issue.:( Sreejith Nair [ My Articles ]
Have a look at this. Its not particulary for the .Net client but it surely gives some hints. In Chapter 16 is explained what deployment options you have. After reading some parts of it I would either suggest the silent install or (a bit more professional) the merge module. Merge modules can easily be integrated in Visual Studio generated setups (just by right clicking on the setup project and selecting add->mergemodule). edit: Merge modules end with .MSM. If you do not find the appropriate merge module fpr the AsaClient in the normal app path then have a look at Program Files\Common Files\Merge Modules.
-
Have a look at this. Its not particulary for the .Net client but it surely gives some hints. In Chapter 16 is explained what deployment options you have. After reading some parts of it I would either suggest the silent install or (a bit more professional) the merge module. Merge modules can easily be integrated in Visual Studio generated setups (just by right clicking on the setup project and selecting add->mergemodule). edit: Merge modules end with .MSM. If you do not find the appropriate merge module fpr the AsaClient in the normal app path then have a look at Program Files\Common Files\Merge Modules.
Thanks a lot. And will get back to you , if everything works fine.:-D Sreejith Nair [ My Articles ]