Tag Info

New answers tagged

0

this is not possible, when you deploy a feature its deployed to the whole web application and is visible to all sites be it site collection feature or site feature. There is no way to hide the feature based on groups/users access rights. The solution that i can think of would be to create a hidden feature, this would then look at the current feature page ...


1

I hope by now you should have got your answer. In case not, below is the solution of the same. I am posting this now as I just now ran into the same problem, but fortunately, I could come out of it pretty quickly,and I think it would be helpful to all other developers like us. Follow the below steps: Go to Solution Explorer on Visual Studio Open the ...


0

It will not affect the Site A unless and untill you deactivate and activate the feature again. Feature affect the site, when you change it state, means if the feature is not available in a particular site and you activate the feature, it will execute the Feature Activastion function and install the changes in the site. If the site already have the feature, ...


1

My question is, will it affect on site A on which we have activated the old feature? The answer is no. Let's say you developed a custom feature F1 which has version 1.0. This is deployed on the farm to all web applications, and activated in site collections where needed. Site collections will have a feature reference that F1 v1.0 is activated in that ...


0

Well i don't think this is a good idea. You are asking to start a exe from workflow. This is against security. This questions has been asked earlier with a nice answer. Have a look at it. Click here However you could start a PowerShell Script using workflow and in that PowerShell script you can call your Console app.


0

Go to the Manifest.xml and add the AlwaysForceInstall="TRUE" to it. This will allow you to deploy your solution now.



Top 50 recent answers are included