Comments on: Change the WSPBuilder DeploymentTarget to WebApplication

By: Waldek Mastykarz

Waldek Mastykarz — Sun, 22 Nov 2009 19:22:44 +0000

@venki: Unfortunately for you, that's the way SharePoint works. After deploying the Solution, the Feature is being copied to the 12 SharePoint directory. From there it is visible to every Web Application/Site Collection/Site in the whole Farm and there is nothing you can do about it.

By: venki

venki — Sun, 22 Nov 2009 17:25:37 +0000

Thanks you very much. I had a small issue when I deployed my solution. I have deployed my solution to one webapplication.

But other applications also showing this feature when I check in the site collection features page. When I activate the feature ..I could see that respective master page in the master page dropdown..and when select it and go to home page ..saying unexpected error. It shouldn\'t show to all applications since I deployed to particular application. Did I do any mistake in my class or?? Thanks in advance.

By: Raghavendra

Raghavendra — Fri, 30 Oct 2009 05:27:50 +0000

Thank you very much. That helped me!

By: Pramesh

Pramesh — Mon, 01 Jun 2009 21:03:21 +0000

Thanks for the post. Very useful.

By: Waldek Mastykarz

Waldek Mastykarz — Tue, 30 Dec 2008 16:08:23 +0000

@liquidpooled: Sweet! Must've missed this one. Thanks :)

By: liquidpooled

liquidpooled — Tue, 30 Dec 2008 15:12:25 +0000

@Waldek – Just place a local copy of the config file (modified however you would like) in the root of your Visual Studio project. This is as of the latest release (http://www.codeplex.com/wspbuilder/Release/ProjectReleases.aspx?ReleaseId=16820) (Search for "local config").

By: Waldek Mastykarz

Waldek Mastykarz — Tue, 30 Dec 2008 14:37:02 +0000

@liquidpooled: Doesn't the .exe.config have to be in the same directory as the exe? If that would work it would be cool indeed! Thanks for the tip :)

By: liquidpooled

liquidpooled — Tue, 30 Dec 2008 13:42:12 +0000

Modifying the WSPBuilder.exe.config file does not have to be a global change. Individual copies of the config file can be maintained for an individual project. By placing a WSPBuilder.exe.config in the root of your Visual Studio project, it will override the global configuration file. I would think this would be preferable, as you can maintain the config file in your SCM, and also maintain all of the options that WSPBuilder affords on a project by project basis.