Useful links for InfoPath form development
Powershell
http://msdn.microsoft.com/en-us/library/ms442691.aspx
http://technet.microsoft.com/en-us/library/ee806878.aspx
http://sharepoint.microsoft.com/blogs/zach/Lists/Posts/Post.aspx?ID=7
InfoPath
http://msdn.microsoft.com/en-us/library/aa943232.aspx
http://blah.winsmarts.com/2008-8-Deploying_InfoPath_2007_Forms_to_Forms_Server_-and-ndash_Properly.aspx
http://msdn.microsoft.com/en-us/library/microsoft.office.infopath.server.administration.xsnfeaturereceiver.aspx
http://www.articlesbase.com/web-hosting-articles/sharepoint-hosting-3-ways-to-deploy-infopath-form-templates-to-sharepoint-2605874.html
http://jopx.blogspot.com/2006/08/infopath-2007-solving-xsn-can-not-be.html
Asp.net tips and tricks
Asp.net tips and tricks
Here is a summary of articles I found very useful over the years while I am working on asp.net
TRULY Understanding View state
http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/Truly-Understanding-Viewstate.aspx
TRULY Understanding Dynamic Controls
ASP.Net 2.0 – Master Pages: Tips, Tricks, and Traps
http://odetocode.com/articles/450.aspx
ASP.NET Tip – Use The Label Control Correctly
http://haacked.com/archive/2007/02/15/asp.net_tip_-_use_the_label_control_correctly.aspx
Asp.net httphandlers
http://www.michaelflanakin.com/Articles/NET/NET1x/ImplementingHTTPHandlers/tabid/173/Default.aspx
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308001
http://msdn.microsoft.com/en-us/library/ms972974.aspx
Asp.net ajax
ASP.NET 2.0 Tips, Tricks, Recipes and Gotchas
http://weblogs.asp.net/scottgu/pages/ASP.NET-2.0-Tips_2C00_-Tricks_2C00_-Recipes-and-Gotchas.aspx
Mastering Page-UserControl Communication
http://www.codeproject.com/KB/user-controls/Page_UserControl.aspx
Comparing Web Site Projects and Web Application Projects
.NET Radio Show
Herdingcode
Clean Code talk
http://www.objectmentor.com/videos/video_index.html
.NET Video Show
.Net User group
http://exposureroom.com/members/RIAViewMirror.aspx/assets/
FAQ
Why should you remove unnecessary C# using directives?
http://stackoverflow.com/questions/136278/why-should-you-remove-unnecessary-c-using-directives
http://codeclimber.net.nz/archive/2009/12/30/best-of-2009-the-5-most-popular-posts.aspx
Create Site Definition in SharePoint2010 Part1
Creating Site definition in Visual Studio2010 is very easy; it has a built-in Site Definition Project template. Today I will show you how to create Site Definition using Visual Studio 2010.You can download the complete source code here.
-
Create Site Definition Project
-
Choose the Site URL and note that you can only choose Farm Solution the sandboxed solution is greyed out.
-
After the Visual Studio did his magic, you can see the Project structure as follows, it contains default.aspx which is the default page for that site definition, onet.xml contains the actions for creating site using this site template(This is like the elements.xml in the feature) and webtemp_Ybbest.CustomSiteDef.xml register this Site definition in the SharePoint(This is similar to the Feature.xml in feature)
-
Open webtemp_Ybbest.CustomSiteDef.xml and modify ID field as it has to be unique and you can optionally choose to modify other fields as well.
-
Deploy your solution and you can find your site template when you creating your site in either Central admin or Site Creation in Site Actions Menu
-
Create your site collection using your new site template and then navigate to the site you will find the site created by using your site definition.
How to fix “A deployment or retraction is already under way for the solution “*.wsp”, and only one deployment or retraction at a time is supported”
I faced this issue when I try to deploy a solution and it failed initially due to SharePoint 2010 Administration service is not started. I then started the service and redeploy the solution; however I face the above issue. To fix it, you need to cancel the current deployment then redeploy the solution.
Problem:
Solution:
To fix it, you need to cancel the current solution deployment. Go to CAà System Settings àManage farm solutions and then cancel the deployment. Next, you can redeployment your solution.
This page cannot be edited in SharePoint Designer
If you try to open a publishing page for editing in Office SharePoint Designer 2010, you see the following message.
This message tells you that publishing pages that are based on a page layout cannot be edited in Office SharePoint Designer 2010, and that their content can be edited only in the browser. To edit the underlying page layout from which the page was created, you can click Edit Page Layout. (Note that you are able to rename pages in SharePoint Designer. To do so, right-click the page in the Folder List, and then click Rename on the shortcut menu.)
However, if you choose, you can edit a publishing page in Office SharePoint Designer 2010 by detaching it from the page layout that it is based on. For example, you might want to customize the Search Results Web Part on a publishing page. You can do so by detaching the publishing page from the page layout, then customizing the Web Part in SharePoint Designer, and finally reattaching the publishing page to the publishing page layout.
For a complete MSDN article, please find from here.
Turn off custom errors for SharePoint2010 sites
By default, SharePoint2010 custom error page is turned on. So whenever you got an exception on a SharePoint page, it displays the custom error page with a correlation ID. You have to search the log file for detailed exception message. To turn off the custom error page, you need to do the following:
Open the web.config file for the specific web application and make the following modifications. (I suggest you to make a backup copy of the file before you start modifying the web.config file)
- Change CallStack=”false” to CallStack=”true” (in safemode element)
- Change debug=”false” to debug=”true“
- Change <customErrors mode=”On” /> to <customErrors mode=”Off” />
*****************Update April 1st 2012**************
In the layout virtual directory in the SharePoint 14 folder,it has its own web.config.You need to change the configuration for custom error as well.
Open the file and change <customErrors mode=”On” /> to <customErrors mode=”Off” />