In TFS 2005, from Team Explorer in Visual Studio, we used to be able to very easily view a documents properties and view the hyper-link. We could then copy this and share it in an email, intranet etc. We have recently upgraded to TFS 2012 using Sharepoint 2010 and I cannot seem to locate document hyper-links.
Is there an easy way to obtain these (without knowing the hyperlinks) or is there another easy way to share content stored in the TFS SharePoint document store? I can do it from the SharePoint Portal easy enough, but I don't really use this, I use Team Explorer and the TFS Web Screens mostly
Many Thanks
this question is quite a bit older, but: maybe I've got an idea?
In each work Item, you have a register "All links"
There you can put the hyperlink to your sharepoint document in. (Button "Link to", Link Type "Hyperlink)
We used this since TFS 2010 and I sumbled over this thread, 'cause we are running into an issue, where these linked documents could not be checked out after opening.
Regards
Jimmy
P.S: maybe, I completely misunderstood?
Related
I'm new to SharePoint development and design. Someone recommended using SharePoint Designer as a quicker way to have the site have a specific look that is different from the SharePoint Look Book. We want sections of our page to have borders with rounded edges, and specific color headers. I found several contradicting articles about using SharePoint Designer. Do you recommend using it on the latest version of SharePoint online in 2022? Have you had any success, or have you encountered any issues?
I enable scripting on my site. I tried connecting SharePoint Designer 2013 to my SharePoint online site successfully, but would like to know if it's a good idea to move forward with it.
As you can read from here SP Designer is supported on the latest On-Premises version of SharePoint(2019) on the bare minimum. But as you can see it is a product that is steadily heading to it's end-of-support/deprecation lifecycle.
Also, as you can understand, since it's development was halted since the 2013 version, a lot have changed since then, and many of the new features are not even supported by SP Designer.
If your are trying to make modifications to a SharePoint Online site, I would suggest using more modern tools(PowerApps, Power Automate, Modern UI, SPFx etc) and leaving SP Designer to it's way to deprecation.
You can also, update your question in terms of what you are trying to achieve and we could propose you some ideas :)
I created a webpart in a sharepoint, tried googiling how the webpart would need to be added to the webpart gallery but couldn't find a good answer or a "how to" how it is done programatically through the activateFeature?. is there an online source which I can follow?
I am not fully clear on your question. Going on an assumption you have developed a webpart using Visual Studio (say 2010 or 2012), then the addition of your webpart to the webpart gallery of your site collection will be taken care of when the solution (the compiled WSP) is deployed (whether you do it through Visual Studio deploy commands, PowerShell etc.) to your target SharePoint instance. If this is not your question, then let us know.
Could someone point out the differences between Sharepoint Designer and the new Design Manager within Sharepoint 2013 ? I searched on the web but haven't found a concrete answer.
Thanks !
1) SPD can still be used to edit SharePoint pages, but the visual Design view and Split view were removed so you need to do all your editing in a code view. You can also still use it for the other things you mentioned.
2) Design Manager is free and included with SharePoint Server. It only works on Publishing sites so its not included with Foundation.
3) Its part of the base installation of the product. You don't need to do anything to procure it.
4) Not really. Design manager provides functionality for Importing/Exporting HTML and CSS that can be edited in any Web Design platform. For example Dream Weaver. Since SPD no longer has a WYSIWYG editor there is not real connection between the two.
5) Most of the customization you've already done will be brought across when you do a content database upgrade. I'm sure there will be some things that need to be upgraded after you do the database attach.
I'm trying to figure out if it is possible to create a custom document library template for SharePoint 2010. When a user clicks on the Libraries link on the quick launch menu of a new SharePoint site, and then clicks the Create button, the Create dialog is launched.
I know this dialog window hosts a Silverlight control, but obviously there is a way to create custom template types in this window. There is even a category that is called Blank & Custom. I've tried copying and modifying the DocumentLibrary feature located in the following location - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES, but that didn't seem to work.
Thanks for reading, I'm sure the answer is obvious but I've been stumbling over Google and MSDN all morning trying to figure this out but I haven't had any luck.
Well, unfortunately the answer is not that obvious. You'll have to create a new List Definition (a document library is actually a list). For that there are several ways, but as a developer, I guess the most common way is to do that through Visual Studio.
A basic tutorial that will guide you through the steps can be found here:
http://msdn.microsoft.com/en-us/library/ms466023.aspx
After you deploy your solution, a new list template (or document library, depending what you created) will show up in the dialog.
Yes, it is not that obvious at all.
Most of the Microsoft documentation is now based on using Visual Studio 2010 and are more focused on the lists than on the document libraries.
By the way, as told by Erwin, document libraries in SharePoint 2010 seems to have become lists, but the lack of documentation regarding the creation of custom lists remains anyway, so after having perform some successful trials I have decided to publish a step by step guide.
Sharepoint 2010 custom ducoment library
Under normal circumstances you cannot move a workflow designed in SharePoint Designer to another site, or into Visual Studio for further customisation/development.
I believe it is possible but was looking for some pointers on approach/technique and maybe some links to more information.
I know some MVPs (Todd Bleeker and others) have been working on this in the past, but I have yet to find a definitive solution to the issue.
Also does anyone know if MS are considering improvements to the Workflow designer within the next version of SharePoint Designer?
Here's a link which might help get you started.
The issue with Sharepoint Designer workflows is that they have essentially hardcoded all the List (and other) GUIDs into them, which just makes it impractical to generalize them.
From what I've heard, you can "just" move the XOML File into a new Visual Studio Workflow and then add the .cs and .rules files, but I also heard conflicting info about this.
I do not know if Microsoft plans improvements, but I also think that SharePoint Designer still has plenty of room for improvements.