I just came across this blog post from John W Powell detailing his experience creating automated builds with VSeWSS 1.3.
Just came across this tutorial for doing web page development and deploying them using VSeWSS 1.3
http://geeksconnected.com/jamil/Lists/Posts/Post.aspx?ID=19
At my TechEd talk last week I showed Visual Studio 2008 extensions for SharePoint 1.3 and I demo'd creating a simple web part that shows data from a SharePoint list in a grid. I also showed command line builds which is one of the features we added in VSeWSS 1.3 and I showed the SPDisposeCheck tool.
For the demos I used the WSS Developer VPC which is available here. I uninstalled the VSeWSS 1.2 that comes on that image and installed the VSeWSS 1.3 from here. I also installed SPDisposeCheck from here.
So that's my machine image to which I also created a sample Employees list and a Projects list in the default SharePoint site. Here's the code that I used in the first demo. Pretty simple stuff.
namespace WebPart1
{
[Guid("64a11214-36e3-4b1a-b8a7-fbb0ca9370c6")]
public class WebPart1 : System.Web.UI.WebControls.WebParts.WebPart
{
public WebPart1()
{
}
protected override void CreateChildControls()
{
SPGridView customerGridView = new SPGridView();
SPWeb web = SPContext.Current.Web;
SPList list = web.Lists["Employees"];
SPQuery query = new SPQuery(list.DefaultView);
query.Query = "<Where><Eq><FieldRef Name='JobTitle' /><Value Type='Text'>SDE</Value></Eq></Where>";
SPListItemCollection items = list.GetItems(query);
AutoAddColumns(customerGridView, list);
customerGridView.DataSource = items.GetDataTable();
customerGridView.DataBind();
Controls.Add(customerGridView);
base.CreateChildControls();
}
private void AutoAddColumns(SPGridView gridView, SPList list)
{
gridView.AutoGenerateColumns = false;
foreach (string fieldname in list.DefaultView.ViewFields)
{
SPField field = list.Fields.GetFieldByInternalName(fieldname);
BoundField column = new BoundField();
column.DataField = field.StaticName;
column.HeaderText = field.Title;
gridView.Columns.Add(column);
}
}
}
}
I'm presenting at TechEd in Los Angeles next week. If you're at the event I hope you'll come to my talk. It is "OFC204 Easy SharePoint Development with VSeWSS 1.3".
The talk is suitable for developers who currently don't work on SharePoint. I will demo the coding of building a simple SharePoint web parts that accesses SharePoint data lists. I will also talk about the types of applications people build on SharePoint, how you can integrate SharePoint development with application lifecycle management tools and about the first SharePoint development best practices you need to know and tools to help you with them.
Find my talk here: http://www.msteched.com/sessionlist/default.aspx
Or find it here: Mon 5/11 | 2:45 PM-4:00 PM | Room 153
I updated my primary machine to Windows 7 RC yesterday. One thing I had to search for and update was Messenger settings so it would minimize to the tool tray instead of the task bar.
Here's the tip.
![SharePointDevPart1_large_ch9[1]_3](http://blogs.msdn.com/blogfiles/pandrew/WindowsLiveWriter/KirkEvansPresentsVisualStudio2008extensi_7EB3/SharePointDevPart1_large_ch9%5B1%5D_3_thumb.png "SharePointDevPart1_large_ch9[1]_3")
Kirk Evans has started recording a series of screen casts for Channel 9 on SharePoint Development. They are great for getting started with the tools and the development environment.
Kirk’s first screencast shows building a simple web part with the Visual Studio 2008 extensions for SharePoint (VSeWSS).
Kirk’s second screencast shows building a low level feature with VSeWSS. Cool how he fixes a bug in his code during the screencast.
For More Information:
VSeWSS v1.3 March 2008 CTP
We have worked hard to listen and respond to the feedback from SharePoint Developers on VSeWSS. After VSeWSS 1.2 released in July 2008 we went out and talked to lots of SharePoint Developers about what they liked and didn't like about developing with VSeWSS. All of the new features in VSeWSS 1.3 are as a result of customer feedback, and there are lots of them. We just finished the VSeWSS 1.3 March 2009 CTP which released a couple of days ago. Read about the new features in the release notes and if there's anything we missed, please tell us.
If you want to see how easy it is to get going with SharePoint Development using VSeWSS, check out Kirk Evans short screecast showing building a Web Part, packaging and deploying it and some of the new features that make workarounds a thing of the past.
If you want to learn SharePoint Development using VSeWSS, check out the hands on labs and training videos at MSSharePointDeveloper.com.
Also released today is a set of 10 new theme projects for VSeWSS. These are individual Visual Studio 2008 projects which when deployed to SharePoint offer fresh new designed themes you can use in your projects.
VSeWSS will continue to be the recommended Microsoft tool for SharePoint Development until Visual Studio 2010 is released including a brand new set of SharePoint Tools. If you are a SharePoint Developer then your feedback about VSeWSS is important to us. You can give feedback on the tool at our Connect site here, or if you want to have a discussion about VSeWSS we recommend the MSDN SharePoint Development forum here. You can also give feedback as a comment on my blog and I will try to reply to anything posted here.
The Release To Web (RTW) of VSeWSS 1.3 is expected in July 2009 and we are not planning any further CTP releases.
If you want even more info about VSeWSS you can learn SharePoint Developer Best Practices direct from Microsoft Patterns and Practices published November 2008 here.
The new version of the Visual Studio 2008 extensions for SharePoint 1.3 include some changes to support install on x64 OS. Specifically it creates a WCF web service that is required to run in x64 and communication with x64 SharePoint. The x86 Visual Studio 2008 makes calls to this web service to do certain SharePoint operations.
The web service is secured so it can only be called by Visual Studio 2008 running on the same machine. We also do not automatically give the web service the required permissions to make calls into SharePoint. The installer notes this, but it's easy to overlook, that you have to add these permissions.
Steve Fox just wrote up a great screen shotted guide for how to do this for Windows Server 2008 here.
Ramp Up (www.MyRampUp.com) is a free online learning program for developers. We’ve just launched a new track: SharePoint for Developers, Part 2. This track, along with the other currently offered ones (eg, Visual Studio 2008), teaches the important skills in a guided path, making the learning process easier and more efficient. The easy-to-access video, written and hands-on content (provided by subject-matter gurus) is specifically tailored for the Ramp Up program, and offered in a variety of forms (article, v-lab, codecast and slidecast). Check it out now at www.MyRampUp.com, and see how Ramp Up can help you become more employable by learning important and marketable skills.
Graduation benefits include discounts from Microsoft Learning.
We want you to answer other peoples questions in the MSDN SharePoint Developer Forum. For the months of March, April and May during 2009 we are running a little challenge for people answering questions on the MSDN SharePoint Developer Forum. For each month an entry means a portfolio of at least ten (10) valid answers posted to the Microsoft SharePoint Developer Forum.
The forum is here: http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/threads/
What are the prizes?
Each month during the Promotion Period, we’ll award the following prizes.
1st Prize - a 120GB Zune
2nd Prize - an Xbox 360 Arcade
3rd, 4th, 5th Prize - a 7” SharePoint Branded Digital Photo Frame
How do I enter?
If you wish to participate in this Contest, you must FIRST register before the close of the Monthly Prize Period you are entering by sending an e-mail to answer@microsoft.com that conforms to the following requirements:
The subject line of your e-mail must read – ‘Forum Promotion’
1. The body of your e-mail must contain the following information:
2. First and last name.
3. Email address
4. Forum sign-in name, which we’ll use to identify your answers.
This is a skill based contest. Must be 18 years or older. Challenge open only to legal residents of Canada (excluding Quebec) or the 50 US states or DC who have technical programming education, experience and/or knowledge necessary to use SharePoint Proucts and Technologies. Challenge ends May 31, 2009. For full details, see official rules including eligibility, entry requirements and judging criteria published here.
I had a problem with a virtual machine I'm building for a demo today and after some time getting frustrated, I did a search and found Alex Riley's blog.
Visual Studio 2008 reported this error "The Application Cannot Start" on startup when run as Administrator, it was working as a regular user but that doesn't allow me to debug.
I copied the two file sthat Alex referred to and it works nicely now. Thanks Alex, that saved me some debugging time.
This week we released an updated CTP of VSeWSS 1.3 here. Let us know your feedback on the Connect Site or on the MSDN SharePoint Developer Forum.
Also today Soma blogged on the Visual Studio 2010 tools for SharePoint and ComputerWorld wrote an article on it here.
We just released the Application Lifecycle Management Resource Center for SharePoint Server. Here you can find answers to common questions about Application Lifecycle Management with SharePoint such as:
- Team Development
- Source Code Control
- Automated Builds
- Continuous Integration
- Build Testing
- Unit Testing and Test Driven Development
- Solution Versioning
The resource center points to a number of new guidance articles, and tools that we have released over the past 6 months or so.
After reviewing this if you still have a question about Application Lifecycle Management for SharePoint Development, then I want to hear about it. Please comment on this blog or send me feedback.
SPDisposeCheck is a tool to help SharePoint Developers follow memory management best practices when using the SharePoint API with IDisposable objects including SPSite and SPWeb. This tool is not supported by Microsoft and is recommended to be used on Developer workstations and not on production SharePoint Server installations.
It was released yesterday at http://code.msdn.microsoft.com/SPDisposeCheck
The tool reviews a .NET Assembly (DLL or EXE) and evaluates SharePoint API's used in that assembly. It will produce a report identifying where code doesn't follow best practices for memory management in SharePoint. It may not find all memory leaks in your code and it may produce false positive results but it does it much faster than you can review source code yourself. The tool checks for guidance published in an update to the MSDN Article (Best Practices: Using Disposable Windows SharePoint Services Objects) that describes the best practices for this area of SharePoint development. This guidance applies only to customers building custom software that they compiled to .NET assemblies that make use of SharePoint API calls. While these messages need expert evaluation in order to determine if the software is not performing properly, in some cases just running the tool on your custom code can lead you to simple fixes that improve the quality and performance of custom code on SharePoint. Customers who are currently experiencing difficulties with memory management in their custom applications should review the guidance listed above. Customers who are currently experiencing difficulties with Microsoft Office SharePoint Server 2007 should contact their regular Microsoft Customer Support Services contact, or refer to http://support.microsoft.com.
note: The MSDN article hasn't been updated at the time of the blog post. The MSDN article should be updated in the next 24 hours.
You are encouraged to discuss usage of this tool on the SharePoint Developer MSDN Forum. You can also provide feedback directly on the CODE.MSDN site for SPDisposeCheck where we published it. We value your feedback on how useful this tool is.
We plan to use Roger Lamb's blog as a place to update the latest guidance for specific cases that come up.
