Caution: Web Application Scoped Features are Activated for All Web Applications by Default

Issue

Each time upon deployment of a package through PowerShell scripts, the web application scoped feature was always automatically activated in ALL web apps. The destination web application specified by -URL in Enable-SPFeature is no use.

Very weird: even though I only deployed the containing solution but no any contained features were activated, this feature was still got re-activated in all web apps.

The Article Saving Life

 
http://www.sharepoint.bg/radi/post/Activate-on-Default-confusion-and-features-scoped-at-Web-Application-level.aspx

When creating SharePoint features in Visual Studio 2010, one of the settings that defaults to True is “Activate on Default”.
There is a lot of confusion as to what this setting actually does:
  • It ONLY applies to features scoped at Farm and Web Application levels. You can still modify it for other features, but it doesn’t do anything.
  • Any feature (Farm or WebApplication) with that setting set to True will automatically activate when you deploy the WSP solution, no matter which way you deploy it (Install-SPSolution, stsasm.exe, Central Administration)

More, http://www.silver-it.com/comment/reply/105#comment-form

The feature property ActivateOnDefault can be set to TRUE or FALSE. It has no impact on web/site scoped features but does have one on WebApplication/Farm scoped features.
When set to FALSE, those features are not automatically activated upon solution deployment but they are automatically deactivated upon solution retraction!
I don’t really understand the added value of that property since for me, it should have a consistent behavior. If you choose not to have them activated automatically, they should not be deactivated automatically…

 After I’ve change it to False, everything is ok !

Comments

Post a Comment

Popular posts from this blog

Use GnuPG Tools or C# Code for PGP Encryption and Signature

For PGP encryption and signature, usually we use PGP command line tools for test purpose and finally use C# application for production. Mine is a Net Core 2.0 console application using NuGet package PgpCore,  https://github.com/mattosaurus/PgpCore. PgpCore is based on BouncyCastle.NetCore which supports the standard OpenPGP keys. Here w use the popular GnuPG (GPG) tools to generate OpenPGP key pair. Download and Install GPG for Windows Download from  https://gpg4win.org/download.html . By default the installation will create two folders (here we use command line tools only): Gpg4Win UI (Kleopatra): C:\Program Files (x86)\Gpg4win Command line tools: C:\Program Files (x86)\GnuPG\bin Generate a GPG Key Pair For GnuPG 2.2.1 and above:     C:\Program Files (x86)\GnuPG\bin> gpg --full-generate-key For old versions of GnuPG:     C:\Program Files (x86)\GnuPG\bin> gpg --gen-key Common GPG Commands List public keys: gpg --lis...
Read more

Errors in Net Core Add-Migration

Visual Studio 2017 version 15.5.2, Net Core 2. Add-Migration error: Exception calling "SetData" with "2" argument(s): "Type  'Microsoft.VisualStudio.ProjectSystem.VS.Implementation.Package.Automation.OAProject' in  assembly 'Microsoft.VisualStudio.ProjectSystem.VS.Implementation, Version=15.0.0.0,  Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable." At C:\Users\wanj\.nuget\packages\entityframework\6.2.0\tools\EntityFramework.psm1:720 char:5 +     $domain.SetData('project', $project) +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException     + FullyQualifiedErrorId : SerializationException Exception calling "SetData" with "2" argument(s): "Type  'Microsoft.VisualStudio.ProjectSystem.VS.Implementation.Package.Automation.OAProject' in  assembly 'Microsoft.VisualStudio.ProjectSystem...
Read more

Set up Visual Studio 2017 for .Net Core Application Development

Image
The Default Profile setting in LibPrograms/Properties/LaunchSettings.json {   "iisSettings": {     "windowsAuthentication": true,     "anonymousAuthentication": true,     "iis": {       "applicationUrl": "http://localhost:8000",       "sslPort": 0     },     "iisExpress": {       "applicationUrl": "http://localhost:49497/",       "sslPort": 0     }   },   "profiles": {     "IIS": {       "commandName": "IIS",       "launchBrowser": true,       "environmentVariables": {         "ASPNETCORE_ENVIRONMENT": "Development"       }     },     "IISExpress": {       "commandName": "IIS",       "launchBrowser": true,       "environmentVariables": {   ...
Read more