it also sounds like you might want to create a site definition that packages your most common features together.īeing a developer, I am usually slanted toward visual studio based customizations because I feel more at home there. By creating a WSP package, you'll be able to deploy features consistently throughout the infrastructure. It sounds like you need a set of features to deploy to each web as you create them. I completely understand the pain with having to do the same tasks over and over for each office. It's a good sign when the users are asking for more. It certainly sounds like you are on the right track. Hopefully someone can open my eyes to the differences, because right now, its just appears to me that Sharepoint designer is for beginners, and Visual Studio is for the experts.
I am not trained in any type of Windows environment development whatsoever, I'm only fairly decent in web languages.
Recently, my boss and I have been tasked with reasearching the pros and cons of rolling out Sharepoint to our entire organization. I've been working with Sharepoint Designer for about 6 months now and been pretty successful in mashing up Javascipt, XSL, and DVWPs to create some interesting webparts in Designer for use on our office intranet. I'm fairly new to Sharepoint administration and customization.
0 kommentar(er)
