We are developing ASP pages for a Windows CE device. We need to debug the ASP pages for reducing the development effort. The ASP pages uses a COM component for getting data from the device. The web server running on the Windows CE device is Httpd.
How can we debug the ASP pages running in Windows CE device?
You've run into one of the many joys of developing using the ASP server that ships with Windows CE. There is usually no way to do live debugging so you're largely relegated to using alert statements or DEBUGMSG from a COM component.
The one exception, and it's not all that easy either, is if you've created your own OS image and you have a BSP with KITL enabled. In that case you can build an OS with the debug version of the web server in it, deploy the OS from Platform Builder, attach with KITL and set break points down in the server code. You can then use those to step into the parsing of your own ASP page. It's a complete headache.
Shameless plug
Attempting to write anything useful with the built-in ASP server is so bad that we actually wrote a complete replacement. Our Padarn Web Server supports a subset of ASP.NET, was designed for CE (though it runs on the desktop as well) and best of all you can use C#/VB.NET and the Visual Studio debugger for your page code behind. The only downside is that it's not free - though if time is of any value, it certainly costs less than trying to use the built-in server.
Related
Good Day everyone
We are currently testing our first Blazor Server application that is deployed on our Staging Server (Windows Server 2016 with IIS 8), we have noticed that, when the application is accessed by multiple users and doing some testing process, the application becomes slow, or sometimes when accessing the site again, the browser still loads the application but without rendering the design, we check it using the dev tools in google chrome, and on the network tab, it says "pending" under the time column.
We tried to ping the application, and it returns without too much latency, I don't know if this application side or on the server or the network, we deploy the project similar to our ASP.NET Core MVC projects, we are all testing the applications on our homes, because of the global pandemic.
Is there a different setup for Blazor Server when deploying to IIS?
I hope someone can help us with this.
Thanks, everyone, and regards.
Edit
We found the suspect, It's the Visual Studio JIT Debugger, yes we install VS2019 on our Staging Server, it's weird that we haven't encounter this from our other web application, is it because the project is in Blazor Server? when we check the server the JIT is running, and then the app is working again, I think when the application encounters an error, this shows up on the server side, and when it reach 3 JIT on the process, it will not continue to load the application.
I search for this and the answers is to disable the JIT Debugger, either in VS or in the register, is disabling this is the best solution??
Thanks again everyone.
In trying to construct a managed debugger in C#, we are using the code from Microsoft.Samples.Debugging.MdbgEngine. The WaitHandle for our MDbgProcess receives signals from the underlying process just fine for console apps, winform apps, and IIS hosted ASP.Net apps on localhost. Once we move the target application, specifically the IIS hosted ASP.Net app to a server 2008 and 2012 OS, the WaitHandle stops receiving signals. We've tried lots of debugging steps, including but not limited to:
Copying dev builds of the application onto the server
Building debugger and target against
AnyCPU
x86
x64
Layering in exhaustive diagnostic messaging
Installing Visual Studio on the server and building everything there
Trying different app pools and different app pool settings
Has anyone ever used these components for ASP.Net on a server OS or have any ideas what might be going on?
https://github.com/SymbolSource/Microsoft.Samples.Debugging
thx
I am developing desktop app using wpf mvvm,however I am confused as to how should I proceed with developing standalone application using sqlite,sql server compact etc
If you need a database (really need a database), I suggest using Entity Framework using the code first approach. This can create a local database for the application w/o the need of a database server.
However, strongly consider if you could just use files in the file system. It is amazing how much you can load into memory and if you want this to run on client machine, you likely don't have so much data that you can't just load the data into memory.
SQL Server Compact requires a separate installation step with administrative credentials.
SQLite is a library that can be compiled directly into the application.
In the case of .NET, it is a part of the System.Data.SQLite package, so it is automatically available when your application is shipped with this package (see SQLite deployment for .net application).
My Classic ASP app is using COM version of ActiveReports to get data out of a very small SQL server 2008 database (less than 200MB) and generating PDFs on request from the simple ASP app. The PDF size is about 8KB. The ASP server runs on W2k3R2 64-bit. I had done the following:
Used regsvr32 in SysWOW64 to register the DLLs
Enabled 32-bit support for IIS running under 64-bit WinOS
The ASP server was on the UAT domain while we were testing, and it used to be able to produce the PDF reports within 5 seconds...then the management decided to 'join' the PROD domain instead; and for some strange reasons, the PDF generation processes took 1-5 minutes instead of seconds. Regardless on unregistering/registering the DLLs again, numerous IIS restarts, adding IUSRS and IWAM users into the local admin group, and re-enabling 32-bit support within IIS, there is no improvements in performance.
Using the SQL profiler, we are 100% sure the bottleneck is not caused by SQL connections, but the generation of PDFs.
We are totally baffling with this problem, is there anything else we should look at, apart from changing server (as a last resort)? Thanks.
pause can be caused by attempt to access to the printer settings in the rendering engine, please try to use MyReport.Printer.DeviceName = "" code before MyReport.Run()
I have to modify an ASP.NET Web Forms application which is currently on production on a Windows Server 2003 in II6.
The problem is that I didn't develop the application and there is not anymore the Visual Studio solution used to develop the application. Moreover the application lies under a website where other applications are running and the connection strings are stored in the global web config file.
I want to modify the application without compromising the version that is actually online.
How can I bring the production version back into a solution file? Many thanks