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
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.
We are migrating a Webforms application based on .NET framework to .NET Core 5. As a part of the process we have decided to break down the single big app into multiple smaller application. As a first step we want to move the Login feature into a separate .NET Core app. This login app will authenticate users and will issue auth-cookie which will be used by the other apps and the old webforms application as well.
For this auth-cookie sharing to work and for other reasons, I need to get all the web apps running on same port but under different virtual directories. For example
http://localhost:5000/ -> This will be the old webforms app
http://localhost:5000/login -> This will be .NET Core login app
http://localhost:5000/admin -> This will be say .NET core admin app
I know we can set this up easily in production environment using IIS virtual applications or with azure front door etc. But we want to enable an all local (no internet needed) development setup which is also very easy to get up and running.
Is it possible to configure .NET core and IIS Express to behave like this on a single machine? All our developers use Windows 10 Home/Pro. Nobody has IIS installed on their dev boxes and we prefer to keep it that way.
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 am newer to Visual Studio 2012 and MVC4, and have a development project of a website using C# and MVC4 and SQL server 2012.
The Publish using web deploy works for the website portion of the project, but it does not automatically update the database portion (schema). If I right click the database portion of the project in VS2012 and click Publish, then the database schema is updated properly. I am only interested in schema updates. What could be wrong?
I programmed my development system to use Web Deploy 3.0. Here is a summary of my configuration:
Computer running win8 x64
SQL Express 2012 as my database server, running as the default instance (i.e. at localhost, NOT as .\SQLEXPRESS)
IIS Express 8 as my webserver, using the "Default Web Site" site (localhost)
Visual Studio 2012 Pro using MVC4 and C#
Web Deploy 3.0
The latest dates are all applied to the software
I programmed an SQL server user WDeployAdmin for managing the database updates and gave it full permissions over the database being used for the website. I also tried using Integrated Security (my administrator login) but that does not help.
I can correctly update the Default Web Site (views and controllers etc) using the Publish feature in VS2012 which uses Web Deploy 3.0.
When I use the Test Connection feature of the publishing setup options, it correctly connects to the database, and that certainly works fine when I do a separate Publish DB operation (right-click DB project, click Publish, and then pick my profile) for that part of my project.
So why doesn't the standard website Publish feature include the database schema updates? The standard website Publish always shows an empty change to database when the schema changes (e.g. a table or a stored procedure).
I have read through much MS docs but nothing is apparent to me.
Any help is appreciated,
Bruce
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.