Bil Simser

2,036 reputation

1820

bio	website	weblogs.asp.net/bsimser
	location	Calgary, Canada
	age	47
visits	member for	3 years, 7 months
	seen	Apr 10 at 12:30
stats	profile views	246

Bil Simser is an independent Solutions Architect with over 15 years in software development. He has helped build many large-scale mission critical systems along the way. In his role as a mentor, he guides clients on how to implement development standards and guidelines, evaluates and recommends new tools and technologies, and helps teams and projects progress into the .NET world. Bil also has a special interest in coaching clients on Agile and General Software Development Best Practices.

Bil has been involved with Microsoft's .NET platform since the early betas and has a deep passion for good Architecture and Software Design. He specializes in SharePoint, .NET, Agile, TDD, and computer game programming. Bil also runs several successful open-source projects. He contributes to the software development community, taking the time to review and edit SharePoint and Agile publications, and speak at user groups, code camps, and conferences, including TechEd, DevConnections, PDC, and DevTeach.

Bil has been a Microsoft SharePoint MVP since 2004 and a member of the MSDN Canada Speakers Bureau. Bil currently lives and works in Alberta, Canada, with his wife, daughter, a Beowulf cluster of computers, every gaming console known to man, and a small menagerie of animals.

	2,036 reputation	bio	website	weblogs.asp.net/bsimser	visits	member for	3 years, 7 months
1820 badges		location	Calgary, Canada		seen	Apr 10 at 12:30

summary answers questions tags badges favorites bounties reputation activity

106 Actions

suggestions reviews revisions comments badges posts accepts all

Mar 27	awarded	Nice Answer
Feb 14	answered	SharePoint Organization Profiles
Feb 5	comment	SharePoint Migration from Dev to Live Thanks for the formatting suggestions!
Jan 19	awarded	Analytical
Dec 7	answered	Adding docs to zipfiles in SP
Dec 5	awarded	Notable Question
Dec 1	awarded	Good Question
Nov 27	awarded	Good Answer
Oct 7	awarded	Yearling
Aug 29	awarded	Notable Question
Aug 16	awarded	Popular Question
Jun 5	comment	Add huge number of folders There is a technical limit yes, but given a design of this nature it's a bad design regardless if you can do it technically. Just because you can do something doesn't mean you should.
Jun 5	comment	Add huge number of folders ++1 I don't recommend this design, even in a file system. Use site collections, sites, document libraries, meta data, views, then finally folders as a last level.
May 31	comment	SharePoint Migration from Dev to Live @BlueChippy Various tools but everything is packaged into a solution in Visual Studio. For example I'll create a feature for a master page with CSS, deply the feature, edit the files in SPD and fold them back into the solution for deployment to an environment.
Mar 27	awarded	Famous Question
Feb 29	awarded	Nice Answer
Feb 9	comment	InfoPath Form Naming Methods This is the process most people do. Just configure the library to allow overwrites when you save the form and you'll be golden.
Feb 9	comment	Clear list data from code Recreating the list is a fairly expensive operation (since you get db hits for deleting the list, recreating it, and adding the items again). Also the list will have a new GUID which might mess some things up (for example if you have some web parts using GUIDs, third party apps, workflows, etc.). Best to use the UpdateListItems batch method above.
Dec 16	comment	Custom Interface vs SharePoint Interface I agree with Wictor, you really can just invest some time in branding SharePoint using HTML/CSS than building your own UI and hooking into SharePoint on the back end. In the end you'll end up having to do a ton of work that you get for free. Yes, SharePoint is complicated but that's because it does a lot. Think of it as a platform with a UI that you can extend and enhance using jQuery rather than something you replace. There are also things that are just going to trip you up like Microsoft Office integration. If you don't need all that, don't use SharePoint and build a ASP.NET app with SQL.
Dec 16	comment	Can I publish a document from one site's document library to another's? Agreed. This is the easiest and you can even have the target library be a read-only one to the users (not the one sending it) so there's no chance of them modifying the document (users will ignore the message about this not being the original document).