Reputation
674
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 6 19
Impact
~64k people reached

  • 0 posts edited
  • 2 helpful flags
  • 76 votes cast
Jul
10
awarded  Notable Question
Jan
29
accepted Redirect on workflow execution
Jan
29
awarded  Popular Question
Dec
19
awarded  Nice Question
Jul
27
awarded  Yearling
Jul
2
awarded  Curious
Jan
13
awarded  Famous Question
Nov
6
awarded  Notable Question
Oct
29
awarded  Caucus
Jan
1
awarded  Notable Question
Nov
21
awarded  Revival
Sep
26
awarded  Popular Question
Sep
18
awarded  Popular Question
Aug
6
awarded  Yearling
Jul
6
awarded  Popular Question
May
4
awarded  Popular Question
Jan
29
accepted Explain it to me: SharePoint deployment scope, solution and features
Jan
29
comment Explain it to me: SharePoint deployment scope, solution and features
Thank you -- this last pointed me in the right direction to find a setting on the package in VS I hadn't noticed before -- the one that determines if it is deployed to globally or to a single web application.
Jan
21
comment Explain it to me: SharePoint deployment scope, solution and features
Thanks, the link was helpful and general guidelines are helpful.
Jan
21
comment Explain it to me: SharePoint deployment scope, solution and features
Thanks. Trying to target solutions for specific web applications, but being required to deploy for all is what started this quest to understand why. It is what triggers this automatic decision by SharePoint that I'm after. Essentially, what is it about hour the feature elements are grouped into features and packaged into solutions that require the solution to be deployed to all web applications? This question, when I looked into it, quickly expanded to understanding feature scoping as well...