Custom SharePoint List View - can I put it in a feature (WSP)? -


Here's my status:

I am working in SharePoint 2007 Enterprise, I have a feature That makes me a list when I apply it and activate it

My adaptations are usually very complex, but I keep things simple. I'm ready to deploy my general workflow solution, to activate, then to open the SharePoint Designer to customize the list. In this situation, let's just say that I edit AllItems.aspx , convert the data view into XSLT data view, then I add a column with static text.

I have used a few different tools (SPSsource, VSESOS, SharePoint Manager, OCD Accessport, etc.) to remove my custom schema.xml and all default views, but I have no luck yet, where the code for AllItems.aspx is now optimized.

When I (using any of the above tools) AllItems.aspx does not differ for example from: & lt; View & gt; element becomes less than a line in schema.xml, for example:

    

I'm really stuck here ... I have no clue what to do. Is this possible? If I include my adaptation at my convenience, then it will save me a lot of time (and documentation).

If any other information I am missing who will help, please tell me ... thank you!


Latest findings :

I have received a little more information in the past few hours. If I save the list as a list template, I can remove my content by saving the .stp file as a .cab file locally. One of the files contains manifest.xml which contains schema.xml as well as some other sections.

One of those sections & lt; Webparts & gt; & lt; for each view in the section. Webpart & gt; is & lt; Webpart & gt; Each of the elements has a very long string of characters ... there is no indication of how these characters actually represent.

The important thing is that I think that any custom footage should actually be web parts if deployed as part of a solution ... but I am not positive.

I encountered a similar problem some time ago. I had to make a very customized view and I had to leave the List Webpart completely, and made my own webpage to present the data.

Generally, when you customize the aspx file in SPDZineer, then all your changes will be in the aspx file and open it in the SPDsiger and you will see all the changes you made. After you convert to the XSL data view, the standard ListFormWebt is replaced by a DataFormWebPart, which can be found in the & lt; View & gt; tag is specified in schema.xml; See itself in the aspx file for ListformWebPart.

Why not make all desired optimizations in the list, save the list as a template (it will include allItems.aspx associated) and then use that template to create your list in your facility? You can add additional columns from the code (if it is dynamic and can not be included in the template), and so on.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -