ClickOnce and System.Data.Entity and GAC
hi all,
i've installed VS 2008 SP1 and every project i rebuild and publish (ClickOnce) requires System.Data.Entity to be registered in the gac.
these project used to work perfectly and wouldn't require SP1 to be executed.
can i target a project simply to work with .NET 3.5 and not 3.5 SP1? is a ClickOnce issue or a VS issue?
how, can i work this around?
thanks in advance
Answers
Yes, W8Man, that is essentially* correct.
And for the sake of completeness, I'll mention that there are other potential new ClickOnce features that would add a dependency to the 3.5 SP1 Framework:
-
The Error URL
-
Suite Name
-
Support for unsigned manifests
-
Support to exclude file hashing
-
All Replies
Hello -
I too ran into this issue. It has to do with the 'Create Desktop Shortcut' option that you can select in the Publish -> Options -> Manifests section of your Project Properties page. This option requires the System.Data.Entity assembly to function, which unfortunately is included in .NET 3.5 SP1.
- Proposed As Answer byBenWhite2008 Friday, April 24, 2009 5:49 PM
Yes, W8Man, that is essentially* correct.
And for the sake of completeness, I'll mention that there are other potential new ClickOnce features that would add a dependency to the 3.5 SP1 Framework:
-
The Error URL
-
Suite Name
-
Support for unsigned manifests
-
Support to exclude file hashing
-
- I just wanted to post that I was getting this same error and removing the 'Create desktop icon' option resolved it for me. On a side note, finding this has saved me so much time that I can go out and actually enjoy life for a few moments instead. Thanks for the great post.
I too had the same issues, but doing as others posted in this blog did not resolve my problem.
What I did learn that if you do have the prerequisition marked for .Net 3.5 SP1, it does not enforce your request. My clickonce app failed to build with the same error.
What I did do, was go to the remote machine and install the newer version of .Net 3.5 SP1, after that my problems went away.
Will Microsoft resolve this issue in SP2?
Davids Learning


