I know I can use PowerShell to install a 2010-solution to the 15-hive.
Is it also possible using <a href="http://msdn.microsoft.com/en-us/library/ms439404.aspx">SPSolution.Deploy</a>[<a href="http://msdn.microsoft.com/en-us/library/ms439404.aspx" target="_blank" title="New Window">^</a>]?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
My question :I have entering the original subject line or content type of the existing email on the text box then click serach button the search button should pull the data original subject line or content type & dislayed on grid.
Search Criteria: Original subject line or content type
Outpput expecting: original subject line data or content type should display on grid .
If its not possible to search both (content type and subject line data )atleast able to search the original subject line data should display on grid.
Is the eMail pushed to a SP-List? Then you just have to configure search for the standard search. For using a WebPart connect two Webparts, one for searching, the other for displaying the filtered list.
Normally not C# Code must be used to get this result.
I'm not really familiar with Primavera 6. But I think there are some ways, you could go.
- Export the Primavera data to Excel (Export to Excel[^])
- Convert it to MS Project. You can directly include MS Project Files in SharePoint (Convert to MS Project)[^]
- You could convert it to XML, too. But I think thats a little more effort.
Ok. There is always a big problem with custom masterpages. That's because you change the "normal" content and it can't be updated automatically. Normaly there is something missing, when an error occurs. So there might be some SPNavigation Elements expecte which aren't there.
There are different ways, to find a solution:
- Create a new custom masterpage for SP 2010
- Take a deep look in the masterpage v4 and compare it to the old one. There must be something new.
- Take a new masterpage and copy your code part for part into it, then you could trace the error. Somewhere something (from the new master page) is dropped that seems to be needed.
I have a project that has a piece that uploads documents to a library in which versioning is turned on. Everytime I add a new document or update a document I get two versions per update call. Here is my code:
'create the spfile itemDim twoXtwoFile As SPFile = twoXtwo.RootFolder.Files.Add(fileName, fileBytes, True)
Dim twoXtwoItem As SPListItem = twoXtwoFile.Item
twoXtwoItem(twoXtwos.Year) = year
twoXtwoItem("Title") = fileName
twoXtwoItem(twoXtwos.Executive) = New SPFieldLookupValue(CInt(Request.QueryString("ID")), execItem(Execs.LookupName).ToString)
Catch ex As Exception
'display an error message
errorMessage.InnerText = "Sorry, but this file could not be added. Please try again or contact the IT Department Help Desk."Finally
The code runs fine, but when I go look at the version history of the document you can see where you have two versions that are the exact same. You really notice on the first upload where you have version 1.0, which is the file itself, and then version 2 that has the same file and the list column items added to it. All subsequent updates just contain two versions of the same update.
The only thing I can think of here is that my code is updating the file first and then going back and adding the list values to the object. Am I right to think that and what can I do so that I only have one version per update/add?
Well, as I see it, you add the file. That is one version. Then you take the file, change it values and update them. That's the second version.
Perhaps it would be a better way, to create the Item and add the file to it, change the properties and the add it to the list. I didn't tried it yet, so it may be wrong, but I think I did it once in that way.
To be honest, it's hard to answer without having a further look on the things you changed. So how do you created the custom master page? Did you use VS or SPD? If you used SPD did you removed one of the Placeholders? That would be a good option for creating errors on display. You should describe what you did and how you did and - that's important for me - which SharePoint-Version you use.