I have the source code of an windows service which is written in VB.NET
I came through various methods to debug this service using development environment (Visual Studio). But the challenge is, I need to deploy it in one of our servers as other application on that server need to access it. The server doesn't contain any development or debug tools. I am not allowed to install visual studio in it.
Is there any other way to debug the windows service on this server?
My intention is to understand the method call hierarchy, as this is a very complex code and I didn't write it. It has a very complex architecture and it is not possible to track the data flow only by looking at it.
If the only restriction is you can't install Visual Studio, I'd suggest you get the Remote Tools for VS 2012, which don't even need to be installed to the server, just a machine with a share accessible from the server. Then follow the instructions.
Related
I need to develop an application for my distributed computing class, with one central server and multiple graphical clients. I was thinking of trying WCF for this, since I am already familiar with making .NET standalone desktop applications using Windows Forms or WPF.
Since I have never worked with WCF before, I am trying to follow a tutorial posted on MSDN, which has defining a service contract as its first major step.* Part of this involves creating a WCF Service Library project, which is supposed to be available as a template under the language of my choice (I am going to use C# here). However, I do not see this project template listed as an option in the new project dialog, and looking for WCF in the search bar returns no results.
How can I make this project template available for use in Visual Studio 2017?
* It should probably be noted that the tutorial mentions that it is written with Visual Studio 2012 in mind. Has anything changed since then that I should be aware of as far as the tutorial is concerned?
Open the installer, choose Individual Components and scroll down to Development Activities. Check the WCF checkbox:
I ended up re-running the Visual Studio Installer to modify my current setup. WCF is not explicitly listed anywhere, but I figured it might have been included as part of the .NET Core or ASP.NET workloads (which were not marked for installation the first time around). After adding these workloads to my installation and restarting Visual Studio 2017, I can now see the WCF project templates listed under C#.
Hi I have a Visual Basic Project Exe which runs fine on a Single Machine i Want it to be Execute for Multi User in LAN. I Have Used Crystal Reports in My Project and database is MS Acess. Please Help me how run the Project in LAN..
A VB EXE is a client architecture which usually needs installing on each client machine using it. The code in the EXE could/would normally then connect to external shared, singular resources over a network (such as databases, reporting servers etc.) but the actual EXE itself would typically be duplicated upon each client computer.
If you need all the users to open the exe and have it always run on the same machine, then you could create client shortcuts or use a script with a CreateObject("application.NameHere","serverToRunAppOn") call &/or modify the DCOM settings for the app through the dcomcnfg tool...
However I'd sugguest instead re-evaluating your architecture. Possibly turning your app into a better practice web-based or MS Access shared MDE+MDB solution for clients to connect to.
I'm actually done doing the small-scale application for our office, however, I really don't have any idea how to deploy this one. Can someone provide me any links on how to do this? This project will be deployed in one pc.
If its a Windows application you need to create a setup project.
If its a web based application, install your application on your web server and provide clients with the appropriate link.
I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals
Is it possible to use SSL with Visual Studio Development Server (a.k.a. Web Application project)? I don't want to have to deploy IIS locally if possible. I'm running Windows 7.
NOTE: I've seen this (http://connect.microsoft.com/VisualStudio/feedback/details/354576/add-https-support-to-visual-studio-asp-net-development-server) but I was still hoping there was a workaround.
It cannot be done with VS 2008, so I've simply resorted to deploying my app to the local IIS as part of the start process with a generated cert.
We can use IIS Express with VS 2010 to develope and test web apps in SSL. Here is a complete article explaning how to use IIS Express and Visual Studion 2010 to develope websites in SSL
Working with SSL at Development Time is easier with IISExpress
Introducing IIS Express
this subject was covered here and it say's, you actually can't.
But you might take a look at this link, which might prove the contrary: (See link in comment, i'm not yet able to post more then 1 link per post ...doh)
Hope this helps.
It can be done in VS2010, I'm not sure if VS2008 supports the following approach. Configure Visual Studio to use use Microsoft IIS Express instead of the web server built in to Visual Studio.