December 7, 2009 at 4:16 am
Recently I got the latest version of one of our products out of Visual SourceSafe. All missing references have been restored and still I can't run the project. The message I am receiving is:
[font="Times New Roman"]'Microsoft.Practices.EnterpriseLibrary.Data.Sql.SqlDatabase' does not contain a definition for 'GetStoredProcCommand' and no extension method 'GetStoredProcCommand' accepting a first argument of type 'Microsoft.Practices.EnterpriseLibrary.Data.Sql.SqlDatabase' could be found (are you missing a using directive or an assembly reference?)[/font]
But ... when editing in the code the function is well known ... parameters and overloads and all.
Somewhere else on the web someone suggested that it might have something to do with the nunit.framework.dll
Does anyone know a remedy?
December 7, 2009 at 7:08 am
Are you sure you have the same version of the Enterprise Library as was used in the project?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 10, 2009 at 1:24 pm
Jack,
Thanks for the response. I finally found out what the problem is!
The case is as follows:
- I had (have) 2 different versions of the EnterpriseLibrary on my PC. The one as was used in the project and a newer version. The version as used in the project was installed especially for this project.
- At first I removed several read-only settings from several kind of files like *.dll, *.xml, *.dll and so on.
- When the dll is writeable the project tries to get a new version. So far no problem.
- The newer version of the dll however was only gathered for one of the six occurrences in the project. All the other versions were maintained as they were.
- After a while I discovered the quite noticeable size difference.
- After correcting them all to one version (the corrected one was again read-only) VS starts uttering that something is ... 'attempting to check out while the build is in progress' and warns for all kinds of dangers.
- After removing the read-only setting and rebuilding again .... you guessed it, a newer version has been placed again.
Only after renaming the newer version of the *.dll to *.dll1 I managed to keep the correct version in my project, to rebuild it all and run the project properly!
So Jack ... in a way you were right! Thanks again.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply