can anyone please help me out, to how to do remote debugging of a DLL (Just a dll) which is independent of the exe.
The dll is a service which will be running in the server machine and the DLL source code is at the client machine. Now when this service is running at the server machine i want to debug the delphi code which is at the client machine using delphi 7.
Compile the DLL with remote debugging symbols and deploy both (.dll, .rsm, etc) on the server machine
Install the remote debugger on the server machine
Start the remote debugger on the server machine
Start Delphi on the client machine and load the DLL project
Start a remote debugging session from Delphi by choosing Run - Attach to process and fill in the server machine
Select the process on the server machine which loaded the DLL
Debug remote
Also see http://delphi.wikia.com/wiki/Remote_Debugger
Related
I have a COM+ application consisting of a client DLL and many middle-tier DLLs.
The application gets run by using an MSC application file.
When I am in die IDE and run my client DLL, I have the following run parameters to launch, run and debug my client DLL (this works great):
The theory is that I should be able to debug my middle-tier by running the DLL with the following parameters (I get the ProcessID from my COM+ Application in Component Services):
Once it is running, I should then be able to start my client MSC application and that should allow me to attach and debug my middle tier. I have seen this working before.
Running my Client DLL from the IDE or as an MSC application works without issues but when I try to debug my middle-tier, as described above, I get a "The RPC server is unavailable" error.
I am running everything locally so I am not sure what server it is referring too.
I have also made sure the following services are up-and-running:
DCOM Server Process Launcher, Remote Procedure Call (RPC) and RPC Endpoint Mapper
Any idea what else could cause this error or what server it is trying to connect too?
It turns out there were more than 1 version of the DLLs registered on my pc. I inherited the pc from a previous employee and noticed some install files of the application on the C drive (all my stuff is on the E drive). I ran the uninstall procedure on the C drive that also unregistered some DLLs and my RPC problem was resolved.
I'm developing a cen/xfs client application in c++ which will register for the events and receive it. I installed the application (.exe file) as a windows service and the system is rebooting after few minutes once i started the service, but when i execute the .exe file directly it works properly. Anyone know why?
I currently have a publish project from my local IIS which is windows 8 and already working but, my problem is I need to transfer it to our VM which is windows server 2008. I need some guidance or recommendation if I need to install Visual studio as well on the VM to publish it or is there any easy way that can simply copy the publish file from my local to VM windows server 2008.
You can publish from your project from local machine visual studio to remote server(in your case VM) if you have access to that server.
Alternatively manually publishing web project is just compiling in release mode with all dependencies & putting code in some IIS site/virtual directory with required Application pool settings.
Microsoft has very comprehensive documentation:
https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/visual-studio-web-deployment/
When I try to deploy my artifact on IIS, I am getting the error as shown in the below screenshot. Any help will be greatly appreciated.
The "IIS Web App Management" screenshot is shown below:
The error message is pretty clear: You can't use it to install IIS on a client OS (such as Windows 10). You have to use a server OS (such as Windows Server).
There's nothing you can do about it other than to use a server OS or use an alternate tool to deploy.
Using Windows Remote Management (WinRM), connect to the host
machine(s) where IIS or SQL Server is installed, and manage the Web
application or deploy the SQL Server Database as described below:
Create a new website or update an existing website using AppCmd.exe.
Create a new application pool or update an existing application pool using AppCmd.exe.
Deploy a Web Application to the IIS Server using Web Deploy.
Deploy a SQL Server Database using DACPAC and SqlPackage.exe.
Your log mentioned the task was installing IIS, and it seemed the tasking was installing IIS on a windows client OS. You need to check your target machine to see whether it has IIS installed.
Alright, I was tasked to develop a Windows Service that listens to a directory for files that are dropped in it, read them, delete them and print out a report.
I installed the service on my work laptop (Win 7 x86) and a test machine (XP x86) under a User account at first. It would do everything as it should except the print the report. No errors, nothing. Then I made it run under Local System and it produced a "No printers found" exception.
Converting the app to a Console Application and running on these machines gave the desired result. OK, so now I was assuming that there are security "stuff" involved.
Then I installed the service on a Server 2008 x64 machine (under Local System) and it just worked. Can anybody explain to me why this is happening? Why does the service allow printing from Server OS but not from a Desktop OS or am I missing something very obvious?
I'm guessing that the printers are installed locally on the server but installed as network printers on the desktop. Local System only have access to local printers.