Comments on: VSeWSS: At Least It Knows CAML http://solutionizing.net/2008/07/09/vsewss-at-least-it-knows-caml/ Random thoughts on custom development in SharePoint. Sat, 12 May 2012 03:45:35 +0000 hourly 1 http://wordpress.com/ By: Scott http://solutionizing.net/2008/07/09/vsewss-at-least-it-knows-caml/#comment-286 Thu, 14 May 2009 15:00:31 +0000 http://solutionizing.wordpress.com/?p=10#comment-286 I’ve used VSeWSS v1.1 (VS2005) and v1.2 (VS2008), as well as seeing the screenshots/previews of v1.3…

Overall, my impressions are:
1) VSeWSS does *NOT* follow traditional development methodologies; it instead follows SHAREPOINT solution (WSP) methodologies. Do not expect an ‘images’ folder to just magically include itself, figure out how SP likes to store images, how VSeWSS maps its components (“items”), and go from there. (following my example, images are stored in 12\TEMPLATE\Images, add the TemplateItem folder, add Images subfolder, (create project subfolder) and drop images.
*note: this seems to be the BIGGEST stumbling block of all dev’s i’ve seen… they want to treat VS/WSP’s like an ASP.Net app that they’ll figure out entirely on their own, when VSeWSS wants to leave the customization to the dev and take care of the SP/WSP “stuff”.

2) support for solution components… some components are just down right difficult to develop (you mentioned the RootFiles stuff, I specifically think of WebServices which need to go into 12\ISAPI, whereas VSeWSS only allows 12\TEMPLATE and below)… though this is being improved in v1.3 (which includes templates for 12-folder level custom components. Adding project assemblies (including a biz layer assembly from a dependent project in the VS solution)… again, 1.3 is going to be changing a *lot* of these limitations.

3) the biggest frustration in the development environment… VSeWSS requires SP, requires Windows Server, which often means Virtual Machines… not a bad idea, as I like a blank slate for each WSP/project i work on… but virtualization includes costs (VPC only supports single thread, VPC/VS support only x86 and no SMP, etc etc).

what VSeWSS does EXTREMELY well:
build/deploy process – VSeWSS automatically performs the build/package/retract/uninstall/install/deploy/reset for SP… this is how packages will be used in production, and mirroring the process is *WELL* worth while… WSPBuilder and others like to assist (command to package)… but often aren’t as well integrated (post-build scripts, etc)… and xcopy’ing to the 12-hive and GAC (even though it’s being added in VSeWSS 1.3) is a somewhat half-assed approach… maybe for some agile stuff, but especially test and final build should use the full process

-Scott

]]> By: Keith Dahlby http://solutionizing.net/2008/07/09/vsewss-at-least-it-knows-caml/#comment-26 Mon, 28 Jul 2008 13:42:10 +0000 http://solutionizing.wordpress.com/?p=10#comment-26 You’re getting a “Cannot find this file…” error because VSeWSS doesn’t know to include the file in the WSP itself. Since you’re modifying manifest.xml, I assume you’re trying to include additional <TemplateFile /> elements, in which case you need to use the “Template” item type. Once you have a “Templates” item in your project, just “Add Existing” to put your file in the appropriate place in the project hierarchy (under IMAGES\MyFeature for a .gif, perhaps). When you deploy the project, VSeWSS will rebuild manifest.xml with the new <TemplateFile /> and know to include it in the WSP.

Chris Johnson describes this process with pictures here.

]]> By: Bob http://solutionizing.net/2008/07/09/vsewss-at-least-it-knows-caml/#comment-23 Fri, 25 Jul 2008 15:43:30 +0000 http://solutionizing.wordpress.com/?p=10#comment-23 Have you found a way to include files (.gifs, ect) in the solution? I am trying to use in the manifest, but get the same error.

but cant get around the error.
“Error: Cannot find this file specified in the manifest file”

]]>