This might be a better question for https://sharepoint.stackexchange.com/, but since i am using TFS there may be differences, i am not sure.
I need to create a dashboard for a couple users that outlines our current sprint queries. They only need to see kind of the same hierarchy we would see if viewing a tree view in Visual Studio's Team Explorer (when running a tree query).
There are Sharepoint 2010 Dashboards.
Referenced here
Edit: Sharepoint 2010 configuration for compatibility explained here will be needed I guess.
Related
I am working on a team that have a number of developers working with SQL Server, developing stored procedures, functions etc.
I would like a consistent layout between the SQL, same header with a copyright etc. SO I need a standard template for the SQL. I know in Visual Studio it is possible to share templates.
How can I generate such a template for SQL Server Management Studio that I can share between developers?
This is how I do it:
the physical location of my template is in(Win7 SQL Server Management Studio 2012):
C:\Users\ys\AppData\Roaming\Microsoft\SQL Server Management Studio\11.0\Templates\Sql
I created my own folder in it (00_Mine)
Created a git repository
Asked other devs to pull from it.
In SQL Server Management Studio, press Ctrl-Alt-T or go to Menu, View, Template Explorer
It will list all the templates. However, from SSMS, there is no easy way to add templates to it by drag and drop, you can create new ones and put them into a folder, such as _WORK_.
The templates live physically in (for 2008 R2): C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\SqlWorkbenchProjectItems\Sql, so you can simply drop files and folders in there or push out to team members using group policy. The templates are sorted alphabetically, hence the suggestion for _WORK_ above. Note: A restart of SSMS is required to pick up Template Folder changes.
Here's an article: Using SQL Server Templates
Question to users of template functionality: do you think it will be helpful if you had a possibility to have placeholders for data like: Current database, Current User, Date/Time (something else ?), so, when you open the template these placeholders would be replaced by appropriate values. I develop an add-in and had this idea a time ago, but I do not know if someone really needs it.
We have Oracle 11g base HR System. Now our requirement is to make some workflow on SharePoint 2010. So we comeup to the decission that we will make webpart to insert, update and retrive records from Oracle and then we will start workflow on that.
So my question was, is it possible to start workflow without is list or document library. If yes than how can I get some idea on that. Some URL where I can find more details.
Kindly let me know if I am going in wrong direction. Please help on that.
You can have site level workflows in SharePoint 2010 which can run without list or a library.
See:
http://www.sharepointbriefing.com/spcode/article.php/3910746/Using-SiteLevel-Workflows-in-SharePoint-2010.htm
However, there is not much information available in the question to evaluate weather its the right option or not. It depends on what is the workflow requirement etc.
I enjoy using SQL Server Management Studio for change and updating my database. Its easier, faster, and safer than writing changes myself.
I was looking into using some sort of version control for databases and read about using a SQL Server Database Project in Visual Studio 2010.
I scripted out an existing database and imported it into a new SQL Server Database Project. Now, from what I can tell, there is no GUI to edit the database; I can't add columns, change datatypes, or edit existing data without scripting it myself. For instance, in SQL Server Management Studio I can right click on a table-name and select "Design" and then add/edit columns, change datatypes, etc from there.
While Visual Studio's Database Projects has some features SQL Management Studio does not have I don't think I can live without a "table designer".
Is there a table designer built into VS's Database Project I'm just not seeing?
No, there's no table designer.
If you're starting to think about version controlling your database, you ought also to be thinking about writing actual SQL to implement your database objects. That's the route that the Database Projects force you down. If you can't write the SQL for your database changes, how are you going to be able to review and appreciate a diff between how a table was 6 months ago, and how it currently is in your project?
I've been using VS2008 Database Projects for about 10 months now for our version control. Every now and then I do still use the table designer, it is a quick and easy tool. I believe the majority of your question centers around workflow as this is what I found to be the most challenging part about development in a version controlled environment. I would recommend continuing to design your objects in Management Studio or however you're comfortable and then do a create script and import that script into your Database project. There are some quirks when doing this, you'll need to always script the create statement even if you're performing an alter in your environment. As well you'll need to remove any USE statements for your database as the context in which you're importing your scripts will always be in the project you're importing to.
We have found that a successful workflow for us to facilitate code deployment is to have a production branch which is branched to a Main (development branch) and then to test. All new development is done in Main and merged by changeset to each other environment as required.
You can import your scripts from your development environment by right clicking in the solution and clicking import scripts. I recommend that you check all the options to overwrite objects that exist, import extended properties and import permissions.
After changing your DB schema using SSMS's GUI tool, you can use Database project's Schema Compare tool to update your project files (set the source to be your database and target to be your project). This way you can keep using GUI tool to manage the schema and the database project will manage the versioning.
There is no visual table designer in Visual Studio 2010 Database Project. But, concerning version control for databases, there is a workaround - you can use SQL Server Management Studio together with Red Gate's SQL Source Control. It costs some money but definitely is worth it.
All my googling returned only information related to how to add additional right click features.
I swear somewhere I saw screenshots of MSS2010 being used where right clicking provided the menu to do various operations, versus having to use the ribbon, or worse that awful menu pictured here.
I was expecting this to all be drag drop... :(
I'm really disappointed with the lack of ajaxy-ness built into mss2010. I can't believe every save/apply reloads the whole page.
SharePoint is a massive product. Microsoft appears to be adding and improving as much functionality as it can in each release.
A high priority of Microsoft for SharePoint 2010 was to redo the HTML for the end user pages. And it is much improved. The poorly formed, table heavy HTML of SharePoint 2007 now has more divs and unordered lists. However, you have stated that you do not like their design choices of the ribbon and full page refreshes. And you also do not like that UI improvements did not extend to system pages in the layouts directory.
SharePoint 2010 was released almost a year ago. Functionality changed during the beta, but it is unlikely that big changes will be introduced at this point. Your two best bets for getting your desired functionality are:
Create a CodePlex project that provides the functionality you want. If the project becomes popular, Microsoft might include it in the next release.
Based on Sharepoint Feature Request, post your request to the SharePoint forums with a subject of "FEATURE REQUEST". If Microsoft agrees to your request, it could be included in the next release.
MacroView specializes in document management, email management and knowledge management solutions based on Microsoft Office and Microsoft SharePoint.
MacroView DMF and MacroView Message add a new pane to Outlook which displays all the areas of the SharePoint environment for which you have access permission. The new pane in Outlook provides:
Searching across the SharePoint DM store with results displayed in Outlook
Formatted previews of files in SharePoint, without the need to download and open
Extensive right-click menu for files and areas
Right-click to create new Libraries and Folders
One-click access to your Favorite document libraries and folders in SharePoint
Automatic creation of Favorites – e.g. for Projects for which you are a timekeeper
Drag & Drop from everywhere to anywhere to save emails or attachments to ANY area where you have permission
Go here for more information
How do I change process template to MSF for Agile on an already existing team project in TFS 2010?
We have upgraded our TFS 2008 to 2010, and now I would also like to change the process template to MSF for Agile (currently CMMI).
We haven't used the workitem functionality much so if some information gets lost in the conversion doesn't matter.
Once you've created a Team Project, you unfortunately can't just upload a new process template. As Robaticus says, you'll have to download the XML for the template and modify it, then re-upload it. The power tool lets you create NEW templates for NEW team projects, but it won't modify an existing one.
Instead, you can use the witadmin.exe tool (on any computer with Team Explorer installed, under \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE, or just from a Visual Studio Command Prompt) to export the current workitem definitions and re-import them once you've made your changes.
Luckily, if you're not using workitem tracking much, then this might not be too difficult. You might be able to just delete all the existing workitem types and then re-upload the new types.
If this is too much trouble, consider how much you want to retain your source control history. It might be worth creating a new Team Project with the Agile template and then just moving all your source code into it.
You can't change the process template, however you can change the work item types. So for bugs, tasks you can swap to the Agile definitions.
You can do this in 2010 with witadmin, in 2008 it's importwit, by first downloading the template to disk (you'll need the TFS power tools for this). Then point the console app at bug.xml, task.xml etc..
Usage: witadmin importwitd /collection:collectionurl [/p:project] /f:filename [/e:encoding] [/v]
/collection Specifies the Team Foundation project collection. Use a fully specified URL such as
http://servername:8080/tfs/Collection0.
/p Specifies the team project in which the new work item type is imported. This is required, except when
the validation-only option is used.
/f Specifies the work item type XML definition file to import.
/e Specifies the name of the .NET Framework 2.0 encoding used to import the XML file. For example,
/e:utf-7 will use Unicode (UTF-7) encoding. Encoding is automatically detected whenever possible. If
the encoding cannot be detected, UTF-8 is used.
/v Validates the XML definitions for the work item type, link type, or global workflow without importing
them.
You can export the agile process template to disk, then import the work items into your existing project. You may need the TFS Power Tools to do this.
I may be too late for this question, but the TFS Integration Platform tools could really help here.
See this question on server fault that details on how to move from Scrum For Team System V2 to Microsoft Visual Studio Scrum 1.0.
You would need to setup your own mappings to move from your templates to the target template, but the process is the same.
Please note witadmin.exe could help in some scenarios but TFS Integration Platform is your ultimate choice to achieve this task. There is a user voice item still pending. Please check this SO thread.
I think the best way to accomplish this is to create a new Team Project with "the new" process template and use the TFS Integration tool to migrate your existing WorkItems and choose create a new branch from Source Control, so you'll have new work Items (with the new workflow) and the source control history (as well). You'd even do this across versions of TFS!! (On the case interested on migrate TFS 2005/2008/2010)
Another way might be to use the WorkItem Templates, but I think this is more a kind-of visual style (I've not much experience) applied to the Work Item. To do so, just right click on your project, import the WITDefinition and apply the template by selecting Apply template on desired WorkITems.