New Posts New Posts RSS Feed: Nuget packate Server add extra entry to web.config
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Nuget packate Server add extra entry to web.config
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
kimj View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 09-May-2007
Posts: 1391 		Post Options Post Options   Quote kimj Quote  Post ReplyReply Direct Link To This Post Topic: Nuget packate Server add extra entry to web.config
    Posted: 24-Sep-2012 at 11:28am
Thanks for reporting these issues.
 
The web.config problems are due to a current NuGet limitation on how it does transforms, so you will see duplicates in the ideablade.configuration section if it was already present, as well as the serviceHostingEnvironment element.  In all cases you can keep your existing config elements and remove the added content.
 
We hope to get the web.config problems, and the problems with additional files such as global.asax and DevForce.cf, fixed in the next DF2012 release.
Back to Top
smi-mark View Drop Down
DevForce MVP
DevForce MVP
Avatar

Joined: 24-Feb-2009
Location: Dallas, Texas
Posts: 343 		Post Options Post Options   Quote smi-mark Quote  Post ReplyReply Direct Link To This Post Posted: 23-Sep-2012 at 1:41pm
I noticed the global.asax issue also
Back to Top
Walid View Drop Down
Senior Member
Senior Member
Avatar

Joined: 14-Nov-2010
Posts: 161 		Post Options Post Options   Quote Walid Quote  Post ReplyReply Direct Link To This Post Posted: 22-Sep-2012 at 4:20pm
Also, installing the package Server to a Domain .net assembly add global.asax to TFS (but not the solution) while this file should only exist on the .web application
Back to Top
Walid View Drop Down
Senior Member
Senior Member
Avatar

Joined: 14-Nov-2010
Posts: 161 		Post Options Post Options   Quote Walid Quote  Post ReplyReply Direct Link To This Post Posted: 22-Sep-2012 at 4:07pm
for information, it looks like the nuget package Devforce Server isn't checking the current configuration of the solution when doing a migration.

It added the entry serviceHostingEnvironment in web.config while one was already there. This cause an error as only one entry is allowed.

In my web.Config my entry looked like this :
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />

it added :
    <serviceHostingEnvironment aspNetCompatibilityEnabled="false" multipleSiteBindingsEnabled="true" />
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down