I have a working wss3.0 + workflow solution, with some aspx forms (followed Robert Shelton’s tutorial) and some document libraries. I would like to deploy it with WSPBuilder but I have stuck hopeless.
The transformation of the workflow was 5 minutes, but I cannot transform workflow-forms at all. I have tried every way I found, but symptoms are constantly same:
The compiler at the codebehind file says “The name 'myAspxTextControl’ does not exist in the current context” for every controls defined in the aspx file.
I tired to connect them on the following ways:
<%# Page Language="C#" AutoEventWireup="true" CodeBehind="Test.aspx.cs"
Inherits="SWEF_WSP.Test, SWEF_WSP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c935c51f6d8e9562" %>
Where SWEF_WSP.dll is my WSPBuilder projects assembly, SWEF_SWP is the namespace, Test.aspx and Test.aspx.cs are my form files demonstrating the issue.
I tried it with and without Codebehind field, and using separate #Asssembly directive too, and changed the the place of these files (in the Layout folder in 12 hive or not ), together, or not, the error is same.
I followed the
http://www.greggalipeau.com/2008/05/23/moving-a-sharepoint-workflow-between-solutions/
(and some more)
But unfortunately didn’t find any buildable example.
I must miss something very evident,
Any help would be greatly appreciated ...
bts
Looks like you are missing the .designer.cs file for the page - Visual studio won't generate it since the project is a workflow, not a website.
Related
Resently started to work with kentico 6.0 .
I have build custom document type with field of "File" type, where administartor can upload file.
Now i'm trying to build a transformation from where site users will be able to download this file:
(like zipped source code of projects in codeproject)
Is where a easy way to do it in kentico?
thanks
You likely need to look into the built-in Transformation methods available to you (found at /CMSHelp/index.html?newedit_transformation_methods.htm of your Kentico instance).
In this case, I think what you want is GetFileUrl(object attachmentGuidColumn)
You'd do something like <a href='<%#GetFileUrl("NameOfTheDataField")#>'>File</a>
I have a web part page "DocLib1.aspx" in document library "DobLib1" and it has few webparts.
How can I take the same web part page and copy it to other document libraries (there are about 50+ document libraries). The web part page is named after the document library (with aspx extension). One of the web part is the list for the same doc lib where the web part is residing.
This worked for me for SharePoint 2010:
Open the site in SharePoint Designer 2010
Right click the page and select copy.
Select a different folder
Rename the page
Move it back to the original folder.
All the WebParts will be intact.
This might seem elementary, but within SharePoint copying a page doesn't copy any of the WebPart on the page. That drove me bonkers. Hope this helps you.
There are two options to copy and paste a Sharepoint 2010 page and retain its web parts:
Perform the copy and paste through Sharepoint Designer 2010.
Access any page in Sharepoint Browser and go to Site Actions > Manage Content and Structure. Copy and paste is possible from here but copy and paste within the same directory can fail; paste in a different directory level then rename the file.
I came upon this site when also looking for a solution to copying a webpart page, but I actually found an even easier way. I've got a library that holds webpart pages, and whenever I need another page that is similar to one of the others in the library, I go to Library Tools > Library in the ribbon, and then Open with Explorer. From there, I simply Copy/Paste the webpart page that is similar to what I want into the same library and then rename the page. Then I can open the new page and make the needed changes.
To add my experience to qhawk's solution (I cant just add a comment directly under the solution as I have less than 50 rep) - in SharePoint Designer 2010, I had to go to Site Objects --> All Files --> then select the relevant Library which has the page you want to copy, copy it to another Library, e.g. Shared Documents, rename it there, copy it back, job done.
I found that if I just selected Site Objects --> Lists and Libraries --> and chose my Library from there, it wouldnt list the actual items in the library to be able to copy them, not even in the Views or Forms box. You have to go through the 'All Files' route.
PS. I know this is an old thread, but I found this whilst trying to find the solution for this, and after finding qhawk's solution needed a little tweaking for me, thought I'd let others know incase someone else stumbles across this.
i am trying to programmatically do some changes in sharepoint as per the link below
in the link below there is a the second cod snippet is a C sharp code. where do i put this code ? or how can i use this code in sharepoint is not mentioned .. can anyone please tell me ?
http://weblogs.asp.net/wesleybakker/archive/2009/03/05/select-multiple-list-items-in-sharepoint-feature.aspx
I haven't tried any of the code out in the post you linked to, but it looks like the C# code just needs to be compiled into an assembly and deployed to the SharePoint server.
The <CustomAction> element in the feature XML below the C# code references this assembly via the ControlAssembly attribute and the compiled class is referenced by the ControlClass attribute.
If you're adapting the code in the post and creating your own project, ensure that your assembly and class names are correctly referenced in the feature XML file (through the ControlAssembly and ControlClass attributes).
Alternatively you can download the author's SharePoint Solution Pack which contains this feature and others.
you should create a new program to call the method
Here's my situation:
I'm working in SharePoint 2007 Enterprise, I have a feature that creates a list for me when I deploy and activate it. My usual workflow thus far has been to deploy the solution, activate it, then open up SharePoint Designer to customize the list.
My customizations are typically pretty complex, but I'll keep things simple. In this case, let's just say that I edit AllItems.aspx, convert the data view to an XSLT data view, then I add one column with static text.
I've used a few different tools (SPSource, VSeWSS, SharePoint Manager, OCDExportList, etc) to extract my custom schema.xml and all the default views, but I have yet to have any luck figuring out where the the code for AllItems.aspx is now that it's been customized.
When I extract (using any of the tools above) AllItems.aspx is no different than the default. The <View> element in schema.xml is reduced to one line, for example:
<View DefaultView="TRUE"
MobileView="TRUE"
MobileDefaultView="TRUE"
Type="HTML"
FPModified="TRUE"
DisplayName="All Documents"
Url="Forms/AllItems.aspx"
Level="1"
ContentTypeID="0x" />
I'm really stuck here... I've got no clue what to do. Is it even possible? It would save me a great amount of time (and documentation) if I could include my customizations in my feature.
If there's any other info I'm missing that would help, let me know... thanks!
Latest findings:
I've found out a bit more in the past couple hours. If I save the list as a List Template, then save the .stp file locally as a .cab file I can extract its contents. One of the files is manifest.xml which contains the schema.xml as well as a few other sections.
One of those sections is a <webparts> section that has a <webpart> for each view. Each of those <webpart> elements contains a really long string of characters... no clue what those characters actually represent.
The important thing is that I think any custom views have to actually be Web Parts if deployed as part of a solution... but I'm not positive.
I have faced a similar issue a while ago. I had to create a very customized view and I had to give up the ListFormWebPart completely, and have created my own webpart to render the data.
Generally, when you customize the aspx file in SPDesigner, all your changes will be in the aspx file itself. Open it in SPDesigner and you will see there all the changes you have made. After you have converted to the XSL Data View, the standard ListFormWebPart is replaced by a DataFormWebPart, which doesn't care about the <View> tags specified in the schema.xml; Look in the aspx file itself for the ListFormWebPart.
Why not do all the customizations you want on a list, save the list as a template (it will include the associated AllItems.aspx) and then use that template in your feature to create your list? You could add the extracolumn from code (if it's dynamic and cannot be included in the template), and so on.
Yes you can. Get the Sharepoint manager tool from Codeplex
http://spm.codeplex.com/
Install it on a machine in your farm, it will allow you to browse the farm via a tree view that shows all objects.
Make the list via the Sharepoint GUI, then browse to it w/ SPM.
SPM will allow you to extract the MOSS/WSS created xml that describes the list view (it shows up in the left hand property grid), which you can then plop into your manifest.xml
I have a similar issue and have been doing a lot of research into this. The dataview web part to me is one of the most powerful components in Sharepoint. Unfortunately I have to provide my solution as a .wsp package and that means that I can not just make the site and use Designer on that site. I have taken a 2 step approach in that I used designer to create my dataview and I also edited the code of that dataview to replace the ListID and Guids to ListName and the actual list name. This allows it to be exported and used in any page/site as long as the list name is the same. I am creating a webpart page document library also in my solution and I believe I can add the pages that have the webparts to this library using the onet.xml file. I will try to get the results of that test in as soon as I can do it.
I am not sure how foolish I am being here!
I have a solution that packages up some master pages and layouts etc which I can deploy fine and the feature appears in the "Site Collection Features" list fine. However I would like to put a custom icon next to my feature. I would like the icon to be in the solution package and so require the image to be put in a list or folder when the solution is deployed (rather than a feature activated).
Is this possible? simple?
There is something about all this sharepoint solution/feature.xml/element.xml I don't grok yet!
It is possible and simple.
In your Feature.xml file, simply include the ImageUrl="" attribute and specify the location of your image. The best practice is to create a folder under the Template\Images folder with your images and then reference this location
Include the folder which contains your images in the solution ddf file
Once deployed, you should have a %12HIVE%\Templates\Images\ACMEImages folder which contains your image
Feature.xml sample:
<Feature
Id="21F724AE-9C1C-4F4D-AAE9-7789CA01A7E3"
Title="ACME Lists"
Description="List definitions for the ACME"
Version="1.0.0.0"
Hidden="false"
Scope="Web"
ImageUrl="ACMEImages\acmelogo.png"
xmlns="http://schemas.microsoft.com/sharepoint/">
<!-- other feature file info omitted -->
DDF file sample:
.Set DestinationDir=IMAGES\AcmeImagesRootFiles\TEMPLATE\IMAGES\ACMEIMages\acmelogo.png
In SharePoint 2010, the Microsoft Default icon is: GenericFeature.gif - a 31 x 22 image. With VS 2010 and SP 2010, you can add a SharePoint "Images" mapped folder to your SharePoint project. Then place your image in this folder. Be sure to provide the Image URL in the Properties panel of the *.feature object. Use a path to the image as noted above.
Pete's solution didn't work for me although I did exactly as he suggests. My problem is that SharePoint is looking for the image in the /_Layouts folder rather than the Templates/Images folder.