It seems that opening a remote website feature is removed in Visual studio 2015. it was present in 2013. as shown in the open website dialog boxes below.
How can one open a remote website residing on a web server in 2015?
Open Website Dialog box in Visual studio 2013/2102
Open Website dialog box in Visual Studio 2015
The "Remote Website" deployment option requires FrontPage Server Extensions, as the dialog states. FPSE enabled WebDAV-like publishing and the Web Folders feature in Windows.
FPSE was last released in 2002 and is now completely obsolete. Very few webhosts support FPSE thesedays so it would be of little use even if VS still supported it.
FTP deployment is far more supported and conceptually far more simpler - so that's why.
WebDAV is a nice design in abstract, but when implemented server-side it's far too complicated to setup and maintain, and doesn't work with modern web-applications because of conflicts with resource-paths. FTP "just works".
Related
I worked for year using CVS source control with Windows Explorer integration using TortoiseCVS which enabled me to view the history of my files in a graphical way and allow me to compare any 2 versions of the file without the need to open IDEs.
Lately I started working in a new place that uses TFS which require me to open Visual Studio every time I want to see the file history.
It would be great to have this level of integration between TFS and Windows Explorer. I wonder if any third party has developed such functionality?
Currently I use C# with Visual Studio 2013.
This is what I see when I choose Revision Graph:
Shell integration can be installed as part of the Visual Studio Power Tools for Team Foundation Server 2013. Make sure you check the "Windows Shell Extensions" option.
To see the revision graph, I am afraid you still need to open Visual Studio and use the Track Changeset feature which seems the closest as far as I can tell.
That and the "Incoming Changes" codelens that was added to Visual Studio 2013 Ultimate and which is going to be part of Visual Studio 2015 Professional and up.
Is it possible to get a standalone TFS client on a server that does NOT have Visual Studio installed? We'd like a way to "reach into" a TFS project from a server, without having to install Visual Studio?
Possible? I've seen Team Explorer, but will that work without Visual Studio?
Team Explorer 2008 will allow you to connect to TFS, but it will install a Visual Studio shell.
Team Explorer Everywhere has Web access. Martin Woodward wrote a great article about it.
Download the TFS power tools. The "Windows Shell Extension" component allows one to perform most operations with TFS via Windows Explorer. Note that the Power Tools installer states that Visual Studio 2010 (or Visual Studio Team Explorer 2010) is a prerequisite for the following features:
Command-line interface
Visual Studio Integration
Check-in Policy Pack
Process Editor
Windows Shell Extension
PowerShell Cmdlets
It's 2017 and Microsoft (re)introduced the standalone Team Explorer.
https://blogs.msdn.microsoft.com/visualstudioalm/2017/04/05/reintroducing-the-team-explorer-standalone-installer/
If you remember back to 2013 (and before), we released standalone installers for Team Explorer. In VS 2015, we did not release a standalone Team Explorer since customers had free options with Express SKUs and Community, which included Team Explorer functionality.
Customers have continued to request a standalone installer for Team Explorer for non-developers, however. And so today, with the Visual Studio 2017 Update release, the standalone Team Explorer installer is back.
Download - https://www.visualstudio.com/thank-you-downloading-visual-studio/?sku=TeamExplorer&rel=15
Included with Team Foundation Server there is a free web front end called "TFS Web Access". In TFS 2008, the Web Access was a different installation and it came as a Power Tool to the TFS. In TFS 2010, the Web Access is installed automatically and is part of the TFS.
In order to get to the Web Access in TFS 2010 do the following:
In your preferred browser type:
http://[YourServerName]:8080/tfs/web/
YourServerName is the tfs name for example: http://tfs-srv:8080/tfs/web/
Also, if you need Agile planning and a Task Board with TFS Web Access, take a look at Urban Turtle - http://urbanturtle.com. According to Microsoft, this is the premier Scrum tooling for TFS.
Discloser: I work with the Urban Turtle team. So do not take my words. Instead, read what Microsoft blogs said about Urban Turtle.
http://blogs.msdn.com/search/SearchResults.aspx?q=urban%20turtle§ions=3652.
There now seems to be a more generic Team Explorer Everywhere for TFS - perhaps that will give us non-VS users desktop access to TFS :)
It includes an Eclipse plug-in and usefully, a command line client.
While it appears to be a dead project. If you like having version control outside an IDE (or independant of the IDE). There is SVN Bridge, which allows you to use TortoiseSVN to talk to your TFS server.
https://svnbridge.codeplex.com/
You can install Team Explorer (on the TFS install DVD, or you can download it from MSDN) without needing to have VS2010 installed - Team Explorer will install a 'shell' VS2010 with only the TFS features available - none of the IDE components.
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fe4f9904-0480-4c9d-a264-02fedd78ab38
As you might know,Visual Studio 2008 has "Copy Web Site to Remote Server" feature. But the problem is every time I open it waits to sync websites (local website and remote website) and makes me wait.
Is there any way to close auto sync on Visual Studio 2008.
Actually I've found a tool named Dispatch which can be downloaded here
But the problem is it's for Visual Studio not Web Developer Express because Express edition doesn't support add-ins and it's for paid which means you have to pay for that and that's what I don't desire :) I hope it works for you guys.
I've issue with VS08. I've got Web Application project (vb.net). Whenever I try to open an aspx or ascx (in Source view - just double clicking on Solution Explorer) the file opens, but VS hangs and is not responding. The only way to restart VS is then by killing it's process. And it happens all the time with these types of files. :/ Reinstall didn't work.
In addition, the only plugin I've installed with this instance of VS is ClearCase source control plugin.
This clearly looks like a problem with the "Microsoft Visual Studio Web authoring Component" program.
Simply pressing Change from Programs and selecting Repair fixed the issue for me.
Now I can use the design look also.
This happened for me when I installed Office 2010.
You should try to remove "Microsoft Visual Studio Web authoring Component" (from Programs).
I had the same problem and removed this component of Visual Studio (more about it here).
You'll loose the visual designer but VS won't hang anymore.
It could be a problem with the "Solution User Options" file (.suo) that lives in the same folder as the solution (.sln) file.
Try checking everything in, closing visual stuido, deleting this file and restarting.
May or may not help - you might not even have a solution after all!
Alternatively, are you using any anti-virus software? Commonly AV is set-up to check files as they are accessed. I seem to remember having issues with ours a while back, and stopping it checking files within my solution helped.
If you use Sophos I can help further, otherwise try stopping your AV scanning your solution's files.
You can try opening using other Visual Studio editor (right-click on the file, Choose Open With...)
There are many cases which may cause your vs2008 to hang. The only experience that caused my VS2008 to hang was right after installing Office2010. Once it happens, the only workaround is to kill Visual Studio in Task Manager. The root cause of this problem is that Office 2007 and the VS 2008 web designer both share a component, 32-bit MSXML5. When Office 2007 uninstalls or gets upgraded ie office2010, MSXML5 is removed yet Visual Studio still needs it.
There are many ways to fix this particular issue
1 - uninstalling Office 2010 and rebooting your machine; the issues will be resolved.
2 - if you still insist on using office 2010 (which will eventually happen) then go to your programs and right click on Microsoft Visual Studio Web Authoring tool and click on repair.
3 - You can simply remove Microsoft Visual Studio Web authoring Component completely from programs. Reinstall "Microsoft Visual Studio Web Authoring Component" from the VS2008 used. You can find the Web core designer from this particular path of your visual studio:
WCU\WebDesignerCore folder and run WebDesignerCore.exe
4 - If you are still experiencing some more issues the link below should sort it out
http://blogs.msdn.com/b/webdevtools/archive/2010/04/19/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang.aspx
Wild shot, but try turning off Html Validation in Options. There was an issue with that at some point.
Turning off Html Validation didn't work. What I've noticed that before opening .aspx/.ascx file in solution memory usage (of VS) is for example 50k and when I double click i.e. Default.aspx to view Source then memory usage goes up to for example 150k and VS is not responding.
Everything did work last week. :/
I was having the same problem... Designer pages when opened hanged the VS.
I use VS2008 SP1.
I had installed Office 2010 AND UPON GOOGLING I FOUND THAT MICROSOFT VISUAL STUDIO WEB AUTORING COMPPONENT needed to be repaired.
If you install VS 2008 Beta on a clean machine, you will find Microsoft Visual Studio Web Authoring Component in the list of installed programs. You will also find that Program Files\Microsoft Web Designer Tools\Office12 and Program Files\Common Files\microsoft shared\OFFICE12 folders with some Office 2007 components even if you don't have Office 2007 installed.
What is Microsoft Visual Studio Web Authoring Component and why does it install Office 2007 components on my machine? The answer is that it is new HTML/ASP.NET design surface that is based on former FrontPages technologies, similar to Expression Web Designer. The designer was made into a separate component, but it was hard to fully separate code from Office libraries. So in VS 2008 designer is installed using separate setup which also installs a few Office libraries the designer relies upon. This means you will get Office 2007 updates offered to you via Microsoft Update although technically you don't have Office 2007 installed. This is because Microsoft Update recognizes shared components and will offer you related updates, so don't be alarmed or surprised. Office 2007 components are fully compatible with Office 2007 so you can freely install and uninstall Office 2007 or VS 2008 and both systems will continue working correctly. Designer is also compatible with Office 2003 and should not be affecting Office 2003 applications. If you observe any disrepancies, please report bug via Microsoft Connect ASAP and we will definitely investigate the issue.
The component can be installed/uninstalled/updated separately. Setup is located on VS DVD in WCU\WebToolsCore folder. If you accidentally uninstalled the component, you can simply run WebToolsCore.exe from the abovementioned folder. The setup does not have UI, simply give it about 5-10 minutes to complete.
An old question, but I bumped into it this week and want to post Microsoft's suggested solution.
ROOT CAUSE
The root cause of this problem is that Office 2007 and the VS 2008 web designer both share a component, 32-bit MSXML5. When Office 2007 uninstalls or gets upgraded, MSXML5 is removed yet Visual Studio still needs it.
WORKAROUND
Workaround if you manually uninstalled Office 2007 AND have a non-Express version of VS 2008. Uninstall and then reinstall “Microsoft Visual Studio Web Authoring Component“. Next run WCU\WebDesignerCore\WebDesignerCore.exe from the install disk.
For more information see MS article:
Upgrade or Uninstall of Office 2007 might cause VS 2008 Web designer to hang
If you don't use the ClearCase plugin do you still get the problem?
i.e. Try saving copying your solution to your local machine, remove all the source control bindings and see if you get the same problem.
Depending on how your environment is set up, you could be looking at a lag when VB is communicating with ClearCase.
And if all else fails, there are a few good diagnostic tools from the old SysInternal suite to help you figure out if it is a file access, registry or network problem.
SysInternals Site
FileMon - File reads / writes
RegMon - Registry reads / writes
TCPView - Network traffic
Does anyone know how you can install/run the TFS Team Explorer in stand alone mode when Visual Studio 2008 is installed on the same machine?
Additional Information: I should have been a little more clear in my question. I'm trying to access the Work Items.
The TFS Team Explorer will always integrate with a version of Visual Studio (apart from Express) if it is installed and there is no way of running it stand-alone.
If you install the TFS 2008 Power Tools, then you can have it so that you get Windows Explorer integration for TFS which many people enjoy. You might also want to look at Team System Web Access to provide a mechanism for accessing TFS from just a web browser (but obviously doesn't include full version control capabilities)
Finally, the company I work for has a completely standalone TFS client called Teamprise Explorer that is implemented in Java, however this is a commercial product.
Hope that helps,
Martin.
The answer is that there really isn't a standalone version. When you install VS Team Explorer on a machine without Visual Studio, the installer will install a Visual Studio shell. Then, when you run Team Explorer in standalone mode, you are actually running a Visual Studio shell.
Martin had a good point about Team System Web Access, which probably would do the job nicely. Plus it has the added benefit that it allows non Visual Studio users access to work items. But, it was decided that it was too much trouble to get permission to install it here (working for the US Army can have its issues).
My solution for now is to run another instance of Visual Studio and access the Team Explorer tools from there.