Visual Studio 2017 Browser Link with custom url - visual-studio-2017

I work on a few websites in different solutions that integrate with each other. To get them to work properly locally, I have to override the URLs. When I change the url from localhost:[port] to local.mydomain.com:[port], browser link no longer works. Can I assume this is a security feature and visual studio won't let me debug javascript unless I'm running as localhost?

Related

Why can't Team Explorer connect?

After having issues with VS2017 Enterprise memory leaks, but none with Team Explorer functionality, I've uninstalled and installed community edition.
tf settings connections shows I'm connected
tf vc checkin works just fine.
where tf shows it is running the 2017 TF.exe
removed my account from both the tfs section, and the vs sign-in in visual studio and added back.
going to the project in a browser at ____.visualstudio.com shows my login works just fine there too.
removed connection from team explorer manager and it no longer has any hosted repositories showing in the Connect to a Project dialog
devenv /resetuserdata as an administrator did not fix it
going in the visual studio baked-in web browser, it comes up as already logged in and shows the projects just fine.
I'm not behind a proxy
deleted project's .suo file
removed stored Microsoft account credentials from Windows 10 credential manager
tried opening vs stand-alone (not opening a project to open it) and connecting
What causes VS2017 to refuse to show VSTS projects?
I experienced the same behavior today with version 15.9.5.
I also tried other options like deleting the VS related folders in %LocalAppData%, etc. to no avail.
The solution is to remove your account from within Visual Studio by selecting 'Account Settings' from the drop-down after clicking your name in the upper-right. Now remove the VSTS account, restart Visual Studio, enter your VSTS credentials anew and voila.

Can not update web reference in Visual Studio 2013

My project in Visual studio 2013 consumes Acumatica web service APIs on another server. I had no problem with adding web reference and calling Acumatica web service API in my code, until recently I added new API into the web service in Acumatica, and then tried to update web service reference in my project. I right clicked on "web service" in Visual studio and then click on "update web reference" to update, however, I was still getting the old APIs, even though I used exactly same URL. I put the URL in browser and I could see the new APIs but when I tried to update, I just couldn't get them into Visual Studio.
When I put that URL into browser to view the WSDL XML, I noticed I only got new APIs after I logged into Acumatica and I was getting old APIs before I logged in. It seems Acumatica only sends updated WSDL xml after users log in, which causes problem to Visual Studio, since there is no way to log in first in Visual studio.
Actually I had successfully updated my web reference before, but almost every time I tried to update reference, I got this problem, then after keeping trying many times, the reference eventually got updated...but this time, the problem seems to just hang on there and doesn't go...
By the way, I tried to go to command line to use wsdl.exe to generate reference class but still got old APIs.
I just don't understand why Acumatica requires logging in to give out new APIs...
If anybody could give me any clue to solve this problem, that would be really appreciated.
(Converting my solution from a comment to an answer)
I believe the Visual Studio GUI frontend for wsdl.exe does allow you to perform a login action (by showing a WebBrowser control) prior to downloading the .wsdl file, but in the event that doesn't work you can always manually download the .wsdl via your desktop browser and then invoke wsdl.exe from the command-line, providing the downloaded file as a command-line argument.

I got following error When i open SiteCore website in Visual Studio 4.0

I got the following two errors when I open Sitecore 6.3 website in Visual Studio 4.0:
Error 1 The virtual path
'/sitecore/shell/Applications/Analytics/ReportRunner/DateSelector.ascx'
maps to another application, which is not allowed.
Error 2 Unknown
server tag 'ds:DateSelector'.
I simply install Sitecore 6.3 (website save into c:/inetpub/wwwroot/sitecoresite/website). When I open this site in Visual Studio 4.0, it shows error.
Can any body tell to me how can I open this or what mistake did I make?
As far as I understand your question, you get the error when you browse the newly installed Sitecore website, which is set up to run under ASP.NET 4.0 application pool. If that's the case, then I should inform you that it is supported to run Sitecore under ASP.NET 4.0 application pools starting from version 6.4.0.
So, you have two options here:
setup your application pool to use ASP.NET 2.0 (make sure .NET 2.0 is installed)
upgrade a Sitecore instance to the 6.4.0+ (which might not be acceptable)
Hope this helps.
I'm not sure if you are having issues because of the way you are opening the project, there are a few issues if you open it as a File-System website project you will want to create a Web Application Project and go from there.
You can look at this blog post :
Simplify Sitecore Visual Studio Project Creation (or the previous version) for information on how to setup a Visual Studio Project correctly for Sitecore.
I actually think this might just be as simple as a missing tilde. So rather having
/sitecore/shell/Applications/Analytics/ReportRunner/DateSelector.ascx
you should have
~/sitecore/shell/Applications/Analytics/ReportRunner/DateSelector.ascx

Pocket PC 2003 application with webservice

I am working on a Pocket PC 2003 application that is referencing a Webservice.
I was figuring out ways to debug the Webmethods but not successful.
-I checked the URL property of the Service in WebReferences and made sure it is correct.
-I started debugging the PocketPC application, then built the Webservice as start without debugging, after that went to Debuh> Attach process and attached devenv-"Pocket PC app"
-I also tried attaching to the aspwp.exe process but couldn't seem to hit the break points in Web Methods.
-The webservice is deployed to IIS virtual directory.
-I copy pasted the entire webservice folder in the virtual directory. Then I am opening the solution file in Visual Studio. Start without debugging, when the webmethods show in browser, click on it, then click Invoke
Can someone guide me the proper way to debug a Webservice of this type? Thanks in advance.
If you're using Visual Studio 2005 or higher, instead of IIS, use the toy Web service that comes with Visual Studio. In the properties of your ASP.NET project with the Web services, under "Web", check the "Use Visual Stuidio Development server". In order to make the toy server start, you have so start the ASP.NET project from Visual Studio.
Then you attach to the process called Webdev.Webserver.exe using Managed code debugging.

ASMX + external dll

I am working on Silverlight client to Microsoft Team Foundation Server. I am using an ASMX web service to make the actual calls using the TFS api.
Everything works fine when I run it with the visual studio development server, but I cannot figure out how to deploy the app to IIS.
I can get the ASMX web service to work unless it is a call that uses the TFS api. I have tried putting all of the TFS api DLLs in like every directory that I can think of, and even installing the visual studio sdk. Nothing works!
UPDATE 11/15/09 7:50PM EST:
Turns out that the TFS api was trying to create a cache at c:\Documents and Settings\Default User\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache\, and the IIS_WPG user didn't have access to do so. Easy fix.
The only supported way of installing the TFS API is to install Team Explorer. You could try to GAC just the assemblies you need, but you're on your own [and technically violating the EULA]...
Other things to check:
IIS is running in 32 bit mode
Impersonation is working correctly
Proxy settings
What error do you get? Have you tried attaching a debugger to IIS?