In Microsoft Visual Studio 2012, there is a pretty good TFS (Team Foundation Service) and in this TFS, you can request code reviews of your work among your peers.
The bad thing is that if you have already checked in your code, it complains and it does not allow you to issue a code review since it sees no changed in the code you have been working on locally.
How do I issue a code review in TFS after I have already checked in code? Can I do it somehow as a comparison to a set of code I checked in earlier? If so, how?
You can right click on a changeset in View History and click Request Review.
There are also links from the View Changeset panel in team explorer.
Related
Last month, I had a Sharepoint addin installed into a clients Project Web Access (pwa) server working quite well.
This month, when I try to compile and run a new version of that same project in Visual Studio, I'm getting a popup asking "Do you want to switch the project to Offline mode?" and if I say 'No', I get a "Communication with the SharePoint server is Cancelled" error when uploading my project.
There have been no configuration changes. The only code changes were to a .JS file (and we reverted those changes, just in case).
There may have been updates to Visual Studio during that time.
I have...
Ensured that the server name is correct and unchanged.
Ensured that the 'Server Connection' property for the project is 'Online'
I can't find any useful diagnostic information anywhere.
Does anyone have any suggestions about how to resolve this, or at least how to get some diagnostic information about why it's happening?
It appears that Office365/SharePoint Online has new defaults that prevent access from external applications ( I was also unable to connect via PowerShell scripting using my Sharepoint Online credentials).
I updated the settings under Policies|Access Control in the Sharepoint Online admin console to allow connection, and now I can connect from PowerShell, and I've got a different issue in Visual Studio.
While I still don't have diagnostic information about communication problems, I've managed to get a little further.
My employer recently upgraded us from VS 2010 to VS 2012. It's been great, but there is one minor annoyance that I'm hoping someone here can help with. In VS 2010 when I switched branches it would ask me whether I wanted to update the IIS paths. Something along the lines of "the path for port:blah is pointing here. Would you like to change it?" VS 2012 doesn't bother asking. It just changes it. I can't seem to find a setting that discourages this behavior, so I'm hoping someone else out there has. Searching IIS on any site brings up way too many results to sift through, especially considering that only one (a topic from this forum, actually) of the first thirty or so had anything to do with IIS and Visual Studio updating the paths (sadly not related to this issue). Any help would be much appreciated.
EDIT: I found the exact message. It reads: "The Web project '...' is currently configured to use the URL '...'. The Web server has this URL mapped to a different folder '...'. Would you like to remap this URL to point to this Web project's folder?"
I took this question to the MSDN forums. I received an answer there so I am just linking this question to the MSDN question.
MSDN forum question
Request on visualstudio.uservoice.com
Just my work around for this problem:
In IIS Manager, I created Sites for each branch, then I configured them using different Ports.
Open each of the web projects in VS2012, then set the properties as:
Start Action = Don't open a page. Wait for request from external application.
Servers = Local IIS
Project URL: http://localhost:[PORT for this site on IIS]
This way, VS2012 will not modify the web port & path. I can still debug with different branches.
Is that helping you ?
Somehow I have changed the TFS 2012 query that is used for code reviews. This query can be found under "My Work" in VS 2012 towards the bottom. I can see the guts of the query by selecting "open query" next to the title "My Code Reviews & Requests" and then selecting "edit query". However, it is not possible to save this query in a way that will change the "My Code Reviews & Requests" or at least I can't see it.
The issue that I have is that someone the query has been changed from the default and I don't know how to get it back to the default. This issue is isolated to me and this specific TFS instance. I can connect to a different TFS instance and see the default query using the same steps as above so I am relatively certain that this issue is related to a specific TFS instance and not my local machine.
Try voting on this Microsoft bug to see if it pushes for an improvement in TFS design by allowing more control over the queries generated by the My Work view:
Queries listed under My Work cannot be corrected
You don't mention how you change that so as I guess you customize the process if so? Of course this happen to existing project but as I guess it will not happen for new project??? if so you can download the existing project that has the issue and create new project using the same process template and try to compare the 2 process to know what is the different and how you can change that.
I use VS2010 on Server 2008 R2 with Sharepoint 2010 Foundation.
I have created a custom master page following instructions from here: http://msdn.microsoft.com/en-us/library/gg447066.aspx (activating my custom page as feature), and was delighted with the results. But as soon as I changed the images and attempted to deploy them through VS2010, I noticed that my changes were not showing in the page (which was still showing the old images).
Useful observations:
It's a Sandboxed solution.
I checked that wsp is built with the new images, and so it was.
When I retract my solution, I also go to Master Page Gallery, and
delete my custom master page from there to make sure I start from
scratch. No difference.
My SP Designer does not give me an option to "revert to site
definition".
My "Look and Feel" section in central admin does not offer a
"reset to site definition" option.
Checking "CustomizedPageStatus" property of the SPFile for my master page shows that it's set to "none", and indeed, calling RevertContentStream throws an exception. This indicates it may not necessarily be the unghosting issue.
Does anybody know where my images get deployed to, and what the cause of this problem may be? The "Deployment Location" property does not lead to the correct location (in fact, I can't even see my Feature's folder). Could it be something to do with the way variables in the path - {SharePointRoot}\Template\Features{FeatureName}\StyleLibrary\Branding101\Images\ - are parsed?
I am new to Sharepoint, so all and any help would be much appreciated.
Since this is a Sandboxed solution, everything gets stored in the content database, accessible through SharePoint Designer 2010. In SP Designer, open the site you are working on, then look under "All Files" in Site Objects: that's where I found my masterpages, images, etc.
Deployment paths (displayed in module properties in VS2010) are just red herring, as no deployment to the file system itself takes place. Hope this helps somebody else!
The SharePoint install is a SP2010 install on a 2008 R2 server. Everything is fully patched. I am running the SP Designer on the SharePoint Server directly.
I have a workflow which is intended to send an email when a new document is created in a custom list. I have deliberately kept the workflow very simple in order to illustrate this problem.
After creating this single step workflow in SP Designer, I click "Check for Errors" and SP Designer reports "The workflow contains no errors".
I then click "Publish" but the Workflow Error dialog is displayed with the message
Errors were found when compiling the workflow. The workflow files
were saved but cannot be run.
Clicking the advanced button reveals more information:
Could not publish the workflow because the workflow configuration file
contains errors
Any suggestions gratefully received
I'll share what fixed it for me - deactivating all workflow features at the site collection level (that is, Workflows, Three-state workflow, Publishing Approval Workflow) and then reactivating the features. I was then able to publish my workflow. This post helped, not sure whether this only works for 365 though, but it's sure worth trying first if you are considering a reinstall.
after googling for quite some time, i think it's an authentication issue. How is your SharePoint set up? Do you use HTTPS for authentication? If so check out this article.
I know this error message from sharepoint. I got this by dealing with multiple lookup fields refering to other lists. Even when I check the worfklow for errors SharePoint says that its all fine but i can't publish it at all.
Try to build a new Test-Site on your Site Collection. Build a Custom Document Library, leave it standard and then set up a new simple workflow just sending a mail.
Fill out the needed fields in mail only using simple values. Send to your mailadress, simple mail subject and simple mail body.
Set the workflow to run only manually.
Try to publish the workflow.
When this is working, then compair to your existing workflow and change your values by trail and error.
After doing a clean install of the OS and SharePoint, workflows are working flawlessly. I can only conclude that the problems were caused by left over registry settings from MOSS 2007. Thanks for the suggestions that people made.
This could also happens if you chage the URL of the web application, all you have do is click the Design button from the library itself.
when changinf the URL from http://server/Site to example: http://server.xx1.net/site, and you try to publish it tries the old url.
what helped in my situation is changing from start workflow automatically to manually.some times answers for critical situation is very easy. hope it helps, many thanks
I ran into this problem and after digging for days and folks suggesting to rebuild the servers, disabling and re-enabling site features, remove previous workflow versions, etc. and trying everything except rebuilding the servers (not practical for clients production environment). I decided to try some tests and found that this issue was only happening on one particular list no matter how simple or complex the workflow was... And when I would check the box for start automatically on item create (or when item changed) it would fail to publish and give the error above, but if I published it with just manually start worked fine. Finally after deleting views and some more testing, I discovered that there was over 240+ columns in this list (I did not create it...) and 50+ workflows set to run on create... Thankfully I have a test environment I built out for the client so I sync'd the Site Collection database back to test environment from Production re-ran my tests and got same error... So what resolved the problem and what was the ultimate cause of the problem, there was to many columns defined in the list and I had to delete several columns to publish the workflow in the test environment. This actually issue translates into the there is a limit in SQL Server on how much data the list can store each type of column takes up so much space read more about it here:
https://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Column
So what I did in production was worked with my client to determine how to break up the list into multiple lists and have relationships between them, thus moving some of the columns and data to another list (Think database/list normalization)... I hope this solution helps someone.