How can I indentify the source of countless server requests being made from Visual Studio to our company server? - windows

I am using VS2019 and work with a vpn that connects me to an internal company server. For some reason that absolutely escapes me (and IT support), 100s of server requests are being made from VS to that server whenever I open a particular project.
It is trying to use my machine name / username to gain access to something on the server side.
I have combed through all the project solution files and dependencies. Nothing that I can find is pointing anywhere other than local.
My question is:
what could be the cause of this?
Is there a way to debug/step through the initialisation of VS when it opens that project?
is there a way to view a log of remote requests (and ideally their response status) being by VS as they occur?

Related

Connection timeout issue in Visual Studio Code

I have been facing some weird connection timeout issues in Visual Studio Code.
I am writing a simple web crawler to read a website using the requests and beautifulsoup4 packages in Python. I don't have any problem opening the URL in my web browsers (opens fine in Edge and Chrome), but when I say request.get(url), then the request always times out. Also, when I try to install some additional packages using pip, it always times out. But the corresponding PyPI page opens fine on my web browser.
The funny thing is - I am facing this issue only when I work out of my company's office. I don't have this issue at all when I am working from my home. There shouldn't be a system-wide firewall or a network firewall, because if there is, then the sites shouldn't be opening on my browsers too, right?
I went to VS Code Preferences and checked the settings there. There's no proxy set up. There is nothing specifically that would block network requests from inside VS Code. Here are some screenshots showing what VS Code Settings looks like.
I looked online and couldn't find much, since every question out there is regarding timeouts in SSH connections, which isn't relevant to me here. This official site here gives a bunch of URLs that need to be allowed by the firewall for VS Code to be able to connect to the network, but I don't know where to add them.
Is there something that I am missing? Any leads on how I can debug this issue? Or is it something that I'll have to take up with my company's network administrator?
TIA.

How to hand over a visual Studio program with a database connection?

After a huge amount of searching I haven't found any information about how to hand over a web project based on entity framework with an SQL Server database connection. The company I do the project for, said I have to give them the whole project to test, but the problem is that I don't know how to give it to them.
If anyone has an instruction for me on how to hand them the project and how they have to install it, it would be very nice. At first I got the project with a test database in a VMware file. I coded the whole program in there as well. But I can't just hand them the VM back in again.
I'm there if you need any further Information (code, database, etc.)
Regards
KSler
I presume what your clients want it to test the web application and not to be in possession the source code.
It thus the case, you can install ngrok on your machine which can then tunnel your localhost application to public accessible application.
Have a look at https://ngrok.com/

Can Biicode publish to a local server (behind the firewall)?

I'm looking at BiiCode for our C++ code, but it appears that you must use the BiiCode cloud as a host. Is there a way in which you keep your dependencies (internal libraries in our case) on a local server? Our team doesn't like having code outside the firewall.
Not yet. Biicode will go open source soon, so you might have to wait until that. We are working on a feature for premium accounts to locally encrypt contents, so the encrypted passwords never hit the server.
(Disclaimer: I work at biicode).

TFS Change server port and visual studio 2012, problems

I have been using tfs with no problems on local network with port 8080. Then i decided to change the port.... why o why did i bother. I have had a terrible few hours trying to sort it. Searched goggle for fixes etc. I think i now have it working but only after reall problems, this then makes me wander and worried about how to from visual studio 2012:
have a local area network conenction to tfs: servername:9876
remote connection: domain name: domain.com:9876
both of which map to the same folders on pc/ laptop and same projects on tfs server.
This caused masses of problems, i then delete the server and re added the correct one. Deleted all cache and workspaces. But then i couldnt map to location as it existed. then couldnt create a new worksapce it said it existed even after delteing the cache. In the end i delete all again, chose a new location on pc for to pull down solutions in tfs. This worked but i am afraid if i look at the solution file in notepad the server port is 8080 still even though the server is now 9876. Based on the above 2 questions what should i do next time. Or even should i still do to make sure all is clean and tidy.
I must have this wrong as it cant be so hard to change the port nunmber of the server or even the server name its self.
thanks
TFS also registers your workspaces and machine names on the server. Run tf workspaces from the command line to figure out which and tf workspace to remove them. That should unblock you. Renaming your local machine (the client machine), or mapping to a different location on your local disk will unblock you.
You should use one single machine name, both locally and remote for the TFS server or map them as if they were different servers. Using both server names completely screws up the local cache, since the API will figure out that they're actually the same server because the Project Collection GUID and the Server ID match.
You could even use a line in your hosts file to be able to always use the same machine name.
I can't find the definitive piece of documentation that tells you to use the same name for all locations, but this blog post comes close. Architecturally, there are no changes between 2010 and 2012.

Does Visual studio Team Foundation Server really need to be on it's own machine?

So we decided to go with visual studio team foundation server for version control, etc. Getting ready to deploy today and read in installation guide:
"You cannot install Team Foundation Server on a domain controller or a computer that is running other server products such as Exchange Server or Host Integration Server."
That and other comments in the guide lead me to think ms does not want me to install tfs on anything other than a server dedicated soley to hosting tfs (ie don't put it on one of my front-end webservers or backend dc).
I am planning on doing a single-server deployment (mostly for simplicity). Can anyone verify that tfs has to be on a dedicated machine? If so, should I virtualize it and hang it off one of the front end machines?
Thanks all...
Performance is pretty important for TFS - check-ins, for example, should be pretty instantaneous or it can have a dramtic impact on developer productivity.
That said - it doesn't need a lot of horsepower - here's a link to the Server Requirements My current client is going "Virtual" - there should be no reason not to - assuming you know how to "tune" your virtual servers to perform equivilantly to the stated hardware specs.
One of the key things to remember, ALL data in TFS is stored in SQL server, so anything running on the same hardware that can affect SQL Server performance will affect TFS's performance. That is why it's important to have Build Server(s) distributed on another machine. Software builds are VERY "File-System" itensive operations and can have a very negative impact on SQL Server performance - hence why it's important to move that off to another "box"
From my experience this is because of the user membership that comes with a domain controller where creating the necessary TFS groups on the domain controller gives incorrect permissions.
However, there is a workaround:
Installation of the TFS Data Tier
Components on a Domain Controller
Copy the contents of \dt in a temp. directory, e.g. C:\TEMP\dt.
Open the file hcpackage.xml in Notepad or any XML capable editor
Search for the phrase “domain controller”.
Change the first WQL after the first match to
<WQL
namespace="\\.\root\cimv2"
query="SELECT * FROM Win32_ComputerSystem WHERE Domain !=''
AND
DomainRole >3"
action="="
count="1"
/>
You have to change count="0" to count="1".
Restart the setup.

Resources