<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.dotnetmafia.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Corey Roth [MVP] : VSeWSS</title><link>http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/VSeWSS/default.aspx</link><description>Tags: VSeWSS</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>VSeWSS 1.3 - Please wait while the installer finishes determining your disk space requirements</title><link>http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/03/03/vsewss-1-3-please-wait-while-the-installer-finishes-determining-your-disk-space-requirements.aspx</link><pubDate>Tue, 03 Mar 2009 20:48:14 GMT</pubDate><guid isPermaLink="false">ceb7fe2a-c56b-4d85-99e6-8dd548580538:856</guid><dc:creator>CoreyRoth</dc:creator><slash:comments>8</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.dotnetmafia.com/blogs/dotnettipoftheday/rsscomments.aspx?PostID=856</wfw:commentRss><comments>http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/03/03/vsewss-1-3-please-wait-while-the-installer-finishes-determining-your-disk-space-requirements.aspx#comments</comments><description>&lt;p&gt;I have been working on creating a new Windows Server 2008 virtual machine lately, so I decided to grab the latest version of &lt;a href="https://connect.microsoft.com/site/sitehome.aspx?SiteID=428"&gt;VSeWSS 1.3&lt;/a&gt;.&amp;#160; I immediately encountered the following error when trying to install.&lt;/p&gt;  &lt;p&gt;&lt;em&gt;Please wait while the installer finishes determining your disk space requirements.&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;The only option is to click the “Return” button and wait.&amp;#160; Unfortunately, it never stops.&amp;#160; After doing a quick Google search, I came across this &lt;a href="http://bloggingabout.net/blogs/harold/archive/2009/01/14/windows-installer-doesn-t-finish-determining-disk-space-requirements.aspx"&gt;post&lt;/a&gt; which describes the issue with MSI packages.&amp;#160; It wasn’t related to SharePoint but put me in the right direction.&amp;#160; This applied to an MSI file though and the VSeWSS download is not an MSI file its an EXE.&amp;#160; I figured there was a command line option to extract the MSI and in fact there is.&lt;/p&gt;  &lt;p&gt;&lt;em&gt;VSeWSSv13_x86_Feb2009CTP_Build_429.exe /extract &amp;lt;workingfolder&amp;gt;&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;Just specify a folder you want the extracted file to go into there.&amp;#160; Then you can execute the MSI file as such with msiexec and the issue does not occur.&lt;/p&gt;  &lt;p&gt;&lt;em&gt;msiexec /i VSeWSS_v13_x86_Build-429.msi&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;Not sure why I ran into this issue, but in case you do, hopefully this helps.&lt;/p&gt;  &lt;p&gt;On a side note, I’m on &lt;a href="http://twitter.com/coreyroth"&gt;twitter&lt;/a&gt; now.&lt;/p&gt;&lt;img src="http://www.dotnetmafia.com/aggbug.aspx?PostID=856" width="1" height="1"&gt;</description><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/Error/default.aspx">Error</category><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/Visual+Studio+2008/default.aspx">Visual Studio 2008</category><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/VSeWSS/default.aspx">VSeWSS</category></item><item><title>VSeWSS 1.3 CTP Feedback and Feature Requests</title><link>http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/02/05/vsewss-1-3-ctp-feedback-and-feature-requests.aspx</link><pubDate>Thu, 05 Feb 2009 21:12:10 GMT</pubDate><guid isPermaLink="false">ceb7fe2a-c56b-4d85-99e6-8dd548580538:833</guid><dc:creator>CoreyRoth</dc:creator><slash:comments>6</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.dotnetmafia.com/blogs/dotnettipoftheday/rsscomments.aspx?PostID=833</wfw:commentRss><comments>http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/02/05/vsewss-1-3-ctp-feedback-and-feature-requests.aspx#comments</comments><description>&lt;p&gt;First of all I would like to say this tool has improved quite a bit since the last version.&amp;nbsp; However, I still feel that it has a long way to go before a SharePoint developer would actually consider using it.&amp;nbsp; The functionality I am targeting today is the web part functionality.&amp;nbsp; Before that, I&amp;#39;ll point out some things I ran into before I could get the product to work at all.&amp;nbsp; &lt;/p&gt; &lt;p&gt;A lot of this is due to the environment I created, but it&amp;#39;s worth pointing out in case someone has a familiar environment.&amp;nbsp; When I installed this particular VM, I chose the quick install to save time.&amp;nbsp; As you know this installs a version of SQL Server Express as well as creates Central Admin and your SSP for you running with the Network Service account.&amp;nbsp; This is where the first issue is.&amp;nbsp; The application pool running the VSeWSS web service has to be a member of the Local Administrators&amp;nbsp; group (Administrators if you are on a Domain Controller).&amp;nbsp; This builtin account cannot be added to that group (to the best of my knowledge), so you have to create a new account (which I prefer anyway) to run the application pool for Central Administration and the VSeWSS site.&amp;nbsp; I did all this and I went into the database and gave this account db_owner permission on the config and central admin content databases and for the most part everything works.&amp;nbsp; I can package a solution and deploy it (however I still get an error activating the feature).&amp;nbsp; This was at least enough to get to the point where I could test it.&lt;/p&gt; &lt;p&gt;Now about using the tool itself.&amp;nbsp; I really like the added options to Deploy, Package, and Retract Solutions added to the context menu of your solution.&amp;nbsp; These all seemed to work really well.&amp;nbsp; I was able to create a quick Hello World web part and deploy it.&amp;nbsp; I activated it manually and was able to view it immediately.&amp;nbsp; One thing, I am very appreciative of is the ability to choose between a Full Trust or Partial Trust web part when you create the project.&amp;nbsp; You still have to specify the Code Access Security settings yourself, but at least it is possible now.&amp;nbsp; I am also a fan of the new options to quick deploy directly to the bin folder and 12 hive.&lt;/p&gt; &lt;p&gt;As a SharePoint developer, I put a lot of files into solution packages.&amp;nbsp; Pages, XML files, Master Pages, Site Template Definitions, you name it.&amp;nbsp;&amp;nbsp; I want to be able to put these files in my wsp.&amp;nbsp; I assumed WSP View would have this functionality.&amp;nbsp; You can get to it by going to View -&amp;gt; Other Windows -&amp;gt; WSP View.&amp;nbsp; Maybe, there is functionality there, but I couldn&amp;#39;t figure out how to add any files to the package.&amp;nbsp; You have no direct access to the DDF file and there are no menu options to allow you to customize or add files in WSP view.&amp;nbsp; There is an option to add another feature, but you can&amp;#39;t customize what files to add along with the feature.&amp;nbsp; Somehow, when you create a new web part project, the .webpart file shows up in the WSP view, but I have no idea how.&amp;nbsp; This by itself, means I can&amp;#39;t use this tool.&amp;nbsp; Again, if I am just being stupid and can&amp;#39;t find it, let me know.&amp;nbsp; The one thing I will note here is that you can customize the manfiest file here.&amp;nbsp; &lt;/p&gt; &lt;p&gt;Another thing, I found lacking is that I can only add one web part per project.&amp;nbsp; Sure, I can manually create another class, but I want it to generate the .webpart file for me and put it in the solution.&lt;/p&gt; &lt;p&gt;Features I would like to see:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Remote SharePoint Server support - Let me install it on a Windows XP machine (without WSS obviously) and specify the URL to my SharePoint server.&lt;/li&gt; &lt;li&gt;Ability to customize contents of WSP file&lt;/li&gt; &lt;li&gt;Better CAS support - A tool to help determine security policies would be great&lt;/li&gt; &lt;li&gt;Multiple web parts in one project&lt;/li&gt; &lt;li&gt;Better control of what goes into the solution package&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;I know the product is just a CTP, so hopefully, with some good feedback we can get a tool we can all use.&amp;nbsp; I guess for now its back to manual creation, stsdev, or WSPBuilder.&amp;nbsp; Microsoft has relied on the community too long for SharePoint tools, it is time they produce.&lt;/p&gt; &lt;p&gt;I have also cross posted this to the &lt;a href="http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/c630bd11-379b-4365-86b1-46c45f3d5059/?ffpr=0"&gt;SharePoint Developer Forum&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://www.dotnetmafia.com/aggbug.aspx?PostID=833" width="1" height="1"&gt;</description><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/Visual+Studio+2008/default.aspx">Visual Studio 2008</category><category domain="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/tags/VSeWSS/default.aspx">VSeWSS</category></item></channel></rss>