Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.
View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 


28 posts

Geek


  Reply # 477282 3-Jun-2011 07:12
Send private message

The procedure entry point ?ConvertExclusiveToShared@cReaderWriterLock3AR@@QAEXXZ could not be located in the dynamic link library MSDART.DLL

Thoughts? 

gzt

10117 posts

Uber Geek
+1 received by user: 1539


  Reply # 477283 3-Jun-2011 07:15
Send private message

btw, which platform are you compiling on? Is that the [win 7] x64 Pro, or something different?



28 posts

Geek


  Reply # 477286 3-Jun-2011 07:20
Send private message

Something different.

I'm compiling on Windows XP x86, Visual Studio 2008 and told it to build for x86.

It works on the following systems:


  • Windows 7 Professional x86

  • Windows XP

  • Windows Vista Home Premium x86

  • Windows 7 Professional x64 (my personal pc at home)


I do have Visual Studio installed on my home computer, that installs a slew of data access drivers doesn't it? Maybe I'll run it on there and use sysinternals to work out exactly what dll its using for odbc. 
 

1221 posts

Uber Geek
+1 received by user: 123


  Reply # 477439 3-Jun-2011 14:49
Send private message

This more of an aside than anything.

Might want to try creating an installer project to test and check dependencies.  Typically I create a  new solution based on the blank template (called xyz), then add my app project (xyz.FormsApp) and then a setup project (xyz.install). 

The installer application(s) can be used for dependency checking and platform targeting.

Another thing, one can also leverage the microsoft provider model to get a list of providers and then use the SqlConnectionStringBuilder (System.Data) to create a connection string. This can be useful when one is referencing a local database.

Just some thoughts.

Andy  
     

           




Software Engineer

 




28 posts

Geek


  Reply # 477650 4-Jun-2011 03:01
Send private message

After all that excitement it was a corrupt MSDART.dll. 

Thanks for all the help guys 

1 | 2 
View this topic in a long page with up to 500 replies per page Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.