Working on a client server solution. Client is one project, server another project. Currently running two instances of vs 2010 one for client and one for server. Manually running server waiting for it to start. Then running client. So far so good. You can start multiple projects in the same sln and I could use this feature but I really want to start the client prj only after the server prj has started. Can I do this ? Worst case is there some way I can delay start of second project by x secs so I can use just one sln. thanks
You can use the "Start Options" of your client project and configure it for run the server first ("Start external program")
Related
Whenever I run a project from Visual Studio and stop running it, I can still request pages, get Data from the Database, add data to it. It's basically working absolutely fine like the project is still running. Also the project has not been published to the localhost and this is not the case only with one specific project it's happening with every project I run from my PC. Why is this happening?
I have a situation : I have two servers (server A and server B) and my TFS making build of my application on server A and should deploy the results on server B. After that it should run UI tests remotely.
For doing that I use TFS 2015 and I added a few steps for my build definition (if you understand what i mean ))) ).
Firs step is "Visual Studio Build" step which is build my project. -> is working fine
The second step is "Publish Build Artifacts" for publishing the build results from server A to server B (maybe it is not best solution for publishing something between machines but is working for me. If you have some advice for that, I will be appreciate to hear it).-> is working fine
Third step is "Visual Studio Test Agent Deployment" which should deploy Test Agent on server B. When this step is runed it shows 'agentlocation' is not a valid path. Ensure that the account with which build agent is running has access to this share. And the all if fails on this step but root to file vstf_testagent.exe is acceseble by everyone (For sharing of this folder was set Everyone Read/Write).
Fourth step is "Visual Studio test using Test Agent" which should run my UI tests. I hope that this step can run my UI tests.
on server A I installed Test Controller and on server B I installed Test Agent and gave him name of Test Controller. On server A I use Visual Studio 2015 but on server B I use Visual Studio 2013.
Please help me to understand problem with third step. What can it be and how to resolve it?
And can step fourth run my UI tests?
Thanks a lot for any help!
The field of "Test Agent Location" is optionally, which is used to supply the path to vstf_testagent.exe from network or local location. If no path is provided, it will be downloaded from network. You can leave this field blank and let it download from network, maybe you can deploy a test agent successfully.
I have a solution with many types of projects, and some of them are websites. Usually, I debug a non-website projects, but everytime I start to debug any project in the solution, the local visual studio IIS starts runnning.
Is there any possible way to stop running the IIS server ???
Thanks!
Open your project and go to the projects Properties. In web apps, you should see a Web tab/choice. Click that, then you can configure which/what server you want to start. I think that the default is that VStudio likes to use it's internal IIS Express, but you can configure it to use IIS locally on the box or to use a custom server.
You can actually set the project to not start anything in the Start Action section on that 'tab' as well, and to simply wait until it registers a connection.
Note that if you are trying to debug using a non-local server, then remote debugging will have to be on on the server, which isn't a great idea in production environments.
Been working some with SharePoint 2010 for a litle while and it feels like my deployment method is way to slow and way to complicated, so my question is basically..
Is there anyway for me to deploy a package to a remote sharepoint server directly from Visual studio?..
For instance.. could I some how create a connection between my visual studio project and the sharepoint server I want to deploy to and then simply press some kind of "Deploy-button" that then deploys the whole project(or even better just my changes) against the remote sharepoint-server?
Thanks in advance!
This won't be easy. Firstly there is the Deploy option which you have for every SharePoint project. This deploys the Solution (WSP) to the URL you specified under Site URL for the project. However this won't help you in your case because it only deploys to a local SharePoint Server.
There simply is no automated way to deploy to a remote server from within Visual Studio. What you are talking about actually has aspects of Continuous Integration -> Continuously wanting to deploy on each check-in.
The perfect tool for continuous integration is the Team Foundation Server. There you will have the possibility to create a deployment script (via a TFS workflow) which automatically increases the version number of your assemblies as well as deploys them to a remote SharePoint server. This usually is done via PowerShell remoting.
PowerShell is the keyword here as in the end you could create your own PowerShell deploy scripts and just call them in the Visual Studio Post-Build instead of using a full fledged TFS.
I created a solution in Visual C# 2010 Express that contains two projects: one is the client, the other is the server. I would like to debug both at the same time, but I can only seem to run one of the projects during debugging.
Is there a way to run both at once?
Go to Solution properties → Common Properties → Startup Project and select Multiple startup projects.
Max has the best solution for when you always want to start both projects, but you can also right click a project and choose menu Debug → Start New Instance.
This is an option when you only occasionally need to start the second project or when you need to delay the start of the second project (maybe the server needs to get up and running before the client tries to connect, or something).