I was facing this issue where i was not able to debug the application which is on server, here i am adding step by step instruction how to achieve remote debugging working.
Step 1. Make Sure Server or Machine from where your application is deployed is having same .net Frame work which you are having on your local system
Step 2. If same Frame work is available then go to your local system path "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE" inside this
One Folder will be present Name "Remote Debugger" copy that entire folder and paste on your Server system.
step 3. Coping the folder is not any location specific just copy anywhere if copying any where is not working then copy it to the "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE"
this path. this folder will have folders
As per your requirement For 64 Bit system use x64 And For 32 Bit system use x86 Folder. others remove
Step 4. Once you done with copy open the specific folder which you kept as per system configuration, Example : I am having 32 bit system will go inside x86 Folder. and open the exe called
"msvsmon.exe" file as administrator.
Step 5. once you open it will show the following window now you are able to connect and debug the remote machine.
Configure Authentication Mode :
For this step refer the below link
https://www.codeproject.com/articles/38132/remote-iis-debugging-debug-your-asp-net-applicatio
Step 6. Open the Visual studio on local machine which will have same version of code which is available on the server machine which you want to debug.
Step 7. Once you open the Visual studio got to the debug -> Attach to Process
Step 8. Once you click on the Attach to process window will get open on the window in qualifier select your server name. once u select that you will see all process of that system below
in that list select "W3svc" service name and click on attach.
Step 9. Put break point on the line of code which you want to debug it will hit when application will run which is hosted on server.
Related
How can I change settings.json (or whatever) so that when I launch VSC, that a workspace (or literally just a directory) opens up automatically.
I have already reviewed this other great answer How to open a default workspace when launching Visual Studio Code?
However I need to do this on brand new, newly provisioned machines that are ephemeral (meaning they get destroyed and recreated from scratch). That means that simply memorizing what I did once, does not help.
Also.... is there a way to do the same thing where the integrated terminal is already open as well? I can't seem to find knobs for either of the above in the settings.json.
This is on linux servers that students will open in their web browser using vs code server.
I'm using Visual Studio 2019 to develop a .NET Core 3 application which runs on embedded Linux. I am able to build the code in Visual Studio 2019. If I copy the binaries manually to the Linux machine and then start the application running there then I am able to attach the Visual Studio debugger to the remote process over SSH in Linux and debug the application. This does work, but it's tedious to deploy it, start it and attach the debugger manually for each debug session. I do have a script in Visual Studio Code which works, but I want to use Visual Studio Professional.
I'm trying to write a Visual Studio Extension so that I can press a key in Visual Studio to have the application built, deployed, started and then connected to the debugger. I would then share the extension with my team. It's very nearly working, except for attaching the debugger.
In the extension I am able to list the processes running in the Linux machine and select my application using this code:
EnvDTE100.Debugger5 debugger = (EnvDTE100.Debugger5)dte.Debugger;
EnvDTE80.Transport transport = debugger.Transports.Item("SSH");
EnvDTE80.Engine engine = transport.Engines.Item("Managed (.NET Core for Unix)");
EnvDTE80.Process2 process = (EnvDTE80.Process2)debugger.GetProcesses(transport, "192.168.11.1").Item("app");
process.Attach2(debugger);
There are two problems:
The call to GetProcesses() opens a dialog where I need to enter the Linux username and press enter, how can I specify the username in code to avoid the dialog appearing?
Even though the selected process looks like the right one (process.ProcessID matches what I see in Linux if I run the ps command), I get an exception when I call Attach2(). The exception message is "Exception from HRESULT: 0x8971001E"
I feel like I'm really close to getting this to work, any suggestions for how to finish it?
I also solved the second problem by changing the parameter passed to Attach2() from debugger to engine, as shown below:
EnvDTE100.Debugger5 debugger = (EnvDTE100.Debugger5)dte.Debugger;
EnvDTE80.Transport transport = debugger.Transports.Item("SSH");
EnvDTE80.Engine engine = transport.Engines.Item("Managed (.NET Core for Unix)");
EnvDTE80.Process2 process = (EnvDTE80.Process2)debugger.GetProcesses(transport, "root#192.168.11.1").Item("app");
process.Attach2(engine);
I found out how to add the user Name, but not the Password:
In GetProcess(), set transportQualifier to $"{userName}#{hostName}".
The 1st time the Window will still Pop up and ask for the Password.
But after that VisualStudio has stored the connection including the password.
My install-shield 2010 is not opening only the splash screen is opened , it was working fine earlier.I have uninstalled it and deleted all the files in app-data,program-files and the registry,im confused if some other app might be blocking this EXE to run (Because it was working properly earlier).
it happen to me from time to time, the problems is usually because the auto reactivation of my licence failed.
their's a tools for that called TSConfig.exe in C:\Program Files (x86)\InstallShield\2015\System.
If it's not that, you can still check in the InstallShield.log in the same directory, it might give you more clues.
EDIT :
I Just found the email that the Flexera support send me back in the day
Close InstallShield
Locate tsconfig.exe on the machine (the default location is:
C:\Program Files\InstallShield\2011\System)
From a command prompt, run the following command: tsconfig.exe /return
Launch InstallShield
If prompted proceed with activation using serial
number
i have TFS express 2015 running on a local machine, i'm trying to get it to run a local process (a calculator window) as a second step after building.
i've tried command line, tried batch script and even tried powershell. the second step seems to go through just fine but no calculator is beeing opened.
is there anything i'm missing here? the TFS Express is installed on the same machine that runs visual studio.
please help!
For XAML build
If you want to open the local process (for example notepad） during Team Build, you need set your Build Service running as Interactively, launch your TFS Admin Console>>Build Configuration>>Build Service Properties>>Stop the service>>selected Run the Service Interactively.
Then you need to customize your build process template to create a InvokeProcess activity. You can use the InvokeProcess activity to start a process (run a program) on the build server. This activity is essentially a wrapper over Start. In your InvokeProcess activity, set FileName = “C:\Windows\notepad”.
After above two steps, you can open the notepad during Team Build. When running your build definition, the notepad will be opened on your build agent machine, and your build keeps on running this open notepad activity. You need logon your build agent using your TFS Build Service account, then you will see the notepad be opened on build agent machine, after you close this notepad, your build will continue run next steps.
I am attempting to launch the windows phone 8 SDK emulator on my Mac so that i can do simple web testing of mobile websites i build.
I have followed several guides and they all say the same thing.
Such as:
6. Once the content (list of files and folders) is displayed, find the VMware virtual machine configuration file – the file with the .vmx extension.
hypervisor.cpuid.v0 = “FALSE”
And this guide proved to be quite useful to get it setup:
http://developer.nokia.com/Community/Wiki/Windows_Phone_8_SDK_on_a_Virtual_Machine_with_Working_Emulator
I was able to get Hyper-V support enabled and I have even managed to open the Windows Phone 8 Emulator directly from the Hyper-V Manager. But in this state it is missing the chroming, the buttons, and when the mouse goes across the screen it disappears. The solution to this is said to be launching the emulator directly from Visual Studio.
My problem is when ever i try to launch the emulator from Visual Studio it creates a new image and then goes into a boot look where it keeps crashing and restarting over and over again.
When viewing the Hyper-V event logs i see this error:
'WP8SDK720P' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0xC000021A, ErrorCode1: 0x88EB9150, ErrorCode2: 0x0, ErrorCode3: 0xC0000022, ErrorCode4: 0xD203BC. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 50607D9A-6E23-4369-9D89-2730614219BA)
How can i get past this error?
In the end I found a solution, I managed to launch the original Windows Phone VM image directly from the commandline with this command:
"C:\Program Files (x86)\Microsoft XDE\8.0\XDE.exe" /vhd "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Emulation\Images\Flash.vhd" /name WP8SDK720P
I created a new text file with notepad and put this command in it and saved the file on my desktop as a .bat file. This way i can just double click the shortcut and launch the sim.
Hopefully this helps someone else out there. In this way, you don't even need to start visual studio to run the emulator, it makes it much simpler if all you are using the emulator for is testing web-apps.
N.B. if you press FN+DOWN-ARROW you can enable the keyboard to work in the sim.
Follow these steps and see if it might help you to fix the problem.
Step 1: Shut down the Guest operating system (Windows 8 in this case).
Step 2: Open the settings for the VM and select Processors. Look at the left pane and see if you have CHECKED the option "Virtualize Intel VT-x/EPT or AMD-V/RVI" under the Virtualization engine section.
Step 3: Open the configuration file (Windows 8 x64.vmx) for the VM and check if you had added the following line of command (hypervisor.cpuid.v0 = "FALSE") to it as shown in the screen shot. You will generally find the file at the location where the virtual hard disk is placed.
If every thing is right, check to see if you had installed Visual Studio 2012 Update 3 (if you are using Visual Studio 2012 as your IDE).
Hope this helps to fix the issue. If you need more information on how to create a VM for developing windows phone 8 apps, there is a great article on nokia developer forum. You can find it here
Happy Coding!!