Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I am new to sharepoint development and need to create some custom NewForm/EditForms for a new custom list I am creating. It seems like I have two choices:

http://community.bamboosolutions.com/blogs/sharepoint-2010/archive/2011/05/12/sharepoint-2010-cookbook-how-to-create-a-customized-list-edit-form-for-development-in-visual-studio-2010.aspx

http://platinumdogs.wordpress.com/2011/12/23/sharepoint-2010-create-and-update-list-forms-programmatically/

Basically, it seems like I can either create the form in sharepoint designer, and then save the entire .aspx and include that in my solution -- or I can add a Feature receiver to make the changes. Or is there another way to do it as well?

share|improve this question

3 Answers 3

up vote 3 down vote accepted

I would recommend to use the first method - Create the Form in SPD, save it in .aspx and include it in a List definition feature.

Benefits

  1. Creating the form in SPD and doing the modifications required are pretty much easy. For eg.- Adding a list view web part or modifying an XSLT would be quiet easier in SPD.

  2. Now, adding .aspx in a list definition in VS and deploying it as a feature should be considered good enough to move it across environments. (DEV -> TEST -> PROD).

Whatever method you have implemented to customize in SharePoint comes handy only if it is packaged and ready to use as a WSP.

share|improve this answer

The 3rd option is InfoPath - if you're in such a position in which you can enable the SharePoint -> InfoPath integration features. Especially useful if forms will later be maintained by staff who are more familiar with Word or Office as the UI will be very familiar to them.

share|improve this answer
1  
Be aware that InfoPath forms don't play nice with managed metadata. –  David Clarke Jul 22 '13 at 23:23

I would go for Deepu's explanation in general.

For more details rather, you need to consider, assuming you build a WSP package via VS2010:

  • Your own custom list? - if yes, you could do it declaratively in the List Definition (is a bitch to do that XML declaratively for the
    views - but is doable).

  • Another list? - use Deepu's explanation with the caveat that you should probably use the a MODULE in VS to deploy it and then update that list's informaiton to point to your new file.

Hope it helps, C:\Marius

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.