C# - Possible To Deploy Application As Desktop Application (with Server Component)
Jul 7, 2010
Question: I created an ASP.NET web application. Now it originally was meant for deployment on a webserver.
That is working, so, so far so good. My question now is: Is it possible to deploy it as a desktop-application, too? That is to say the installer installs some kind of server, plus the web application, configures the server to run this application on a localhost URL, and then creates a link in the start menu/desktop, where it opens that url (website, the application) on localhost in a web browser?
I think it should be possible, though the server wouldn't be IIS, because this is a windows component which can't be separately installed. Is there anything like this already out there? The nonplusultra would be that it only starts the server when you click on the shortcut.
I have finished developing an executable desktop application to generate a fractal image based on the passed-in arguments. The output type is JPEG.Now I am developing a site under ASP.NET MVC 3. I want to use the executable from within my site.
Is it possible to use it as is without converting it to a class library and recompiling?
Apologies if this seems obvious, but after a week searching I can't find a clear answer to my problem.
I have developed an application in Visual Web Developer 2010 Express that uses the asp.net application services membership provider. It works well in development on my machine (data in the ASPNETDB.MDF database).
I packaged my application and deployed the relevant files with FTP to my shared hosting provider.
I took a copy of the ASPNETDB.MDF and restored it to the SQL Server 2008 on my shared hosting. I can connect to this through the Database Explorer in Visual Web Developer, but it doesn't contain any schema or data.
I know once I have the database in production I will have to make sure the connection string in web.config is poiting to it, but I don't know how to get the DB to production in the first place.
I have an application which has a website and a project. The project contains an executable file which I'm trying to run as a process from the website's Global.asax file's application_start(). When I run this application from localhost, everything runs smoothly but when I deploy the application on IIS, application_start's code is executed and I can see the process name in the taskmanager but I cannot see the window which the console application normally starts in (when i run the application on localhost) and neither is the code executed.
Here's what I'm doing:
-- copied website and project in wwwroot -- made a virtual directory of the website -- when i run the website, I see the process in taskmanager but the code is not executed.
I am new to deployment and IIS, and would really appreciate I someone could tell me what i'm missing
I have developed web application i need to deploy it on remote server.i am using asp.net 3.5 ,c# 3.0 and visual studio 2008,sql server 2005.using visual studio 2008 how i can make msi file to deploy application on server
I have two webservers in a cluster serving a web application. Using MS Web Deploy to push a new version of the application to one server, and then again to synchronize the files to the other server in the cluster. It seems to be the most ordinary thing to do. But wouldn't there be a problemm, when one server is deployed with the new version, and the other is not yet finished. Will it not cause troubles, when a page loaded with the new version makes a webservice request and the balancer sends the request to the server with the old version?
What's the best way to avoid this? I thought about scripting a drainstop of the server, that we deploy to, and make sure only one server is running at a time. But I can't find anyone else, who seems to have written about such a solution. And guess that it doesn't scale very well too. Another solution could be to shut down all servers when updating. But that doesn't seems very clever.
I have developed a web application with ASP.Net 2.0 (VB Code Behind) and I am using My SQL as database.
I wish to sell the web application from my other website to multiple users. What would you suggest to be the best way to deliver this application? Fact is I can compile the front end script and provide the compiled version but I am not sure how to provide the associated MySQL database to them. I need to make sure that the buyers are not able to alter any code in the application or modify the preset data in the MySQL database. I do not wish to use the Setup Based deployment method as it will require the buyers to have administrative rights on the server, which may not be available on shared hosting.
But at the same time they must be able to get the web application up and running with minimal effort. I must be honest with you that I have developed only HTML based static websites till now and this would the first time I am launching an ASP.Net application.
for the last couple of days i've been trying to deploy an application that uses a sql express db on to my iis.up until now i was trying to upload it onto iis 5.1, but now i a brand new iis7.5 but i still get this annoying error:An attempt to attach an auto-named database for file C:application_nameApp_DataDatabase1.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.needless to say that there is no database with this name on my computer. i've set the application pool to .net framework 4.0.
We have a huge ASP.NET web application which needs to be deployed to LIVE with zero or nearly zero downtime. Let me point out that I've read the following question/answers but unfortunately it doesn't solve our problems as our architecture is a little bit more complicated.
Let's say that currently we have two IIS servers responding to requests and both are connected to the same MSSQL server. The solution seems like a piece of cake but it isn't because of the major schema changes we have to apply from time to time. Because of it's huge size, a simple database backup takes around 8 minutes which has become unacceptable, but it is a must before every new deploy for security reasons.
Currently the best idea we came up is buying another SQL server which would be set up as a replica of the original DB. From the load balancer we would route all new traffic to one of the two IIS webservers. When the second webserver is free of running sessions then we can make deploy the new code. Now comes the hard part. At this point we would go offline with the website, take down the replication between the two SQL servers so we directly have a snapshot of the database in a hopefully consistent state (saves us 7.5 of the 8 minutes). Finally we would update the database schema on the main SQL server, and route all traffic via the updated webserver while we are upgrading the second webserver to the new version.
also share your thoughts regarding this solution. Can we somehow manage to eliminate the need for going offline with the website? How do bluechip companies with mammuth web applications do deployment?
Edit 1 (2010.01.12):
Another requirement is to eliminate manual intervention, so in fact we are looking for a way which can be applied in an automated way.
Let me just remind you the requirement list:
1. Backup of database 2a. Deploy of website 2b. Update of database schema 3. Change to updated website 4 (optional): easy way of reverting to the old website if something goes very wrong.
I have developed a Web and windows application, both in C#.NET. Now, what I would like to do is when a button is clicked on a particular page in the web application, a signal has to be sent to the windows app saying a link has been clicked. How could I do this really easily? I would like to stay away from socket programming...
I thought of the web app storing cookies and the desktop application monitoring the cookies folder but that seems a bit clumsy.
Can someone point me to a step-by-step guide on how to deploy ASP.Net applications to a totally empty and brand new Windows 2003 Server?The server has ASP.Net and the .Net framework installed on it. IIS is up and running. I have created a new application pool.
I'm trying to deploy my MVC 2.0 web application to a Windows 2003 server with IIS6, and can't find the means to do it. I read about clicking Build/Deploy, but I don't have this showing on my menu, and I have the professional version.
I just added System.Web reference to a dll assembly, the assembly is for windows applications and for web applications. IF the assembly will be deployed on a server, System.Web will be shared using GAC, and there is no overhead. But what about windows clients. I am wondering if there are extra resources or any kind of problems when System.Web is loaded into memory?
I am developing one Intranet Que type project for a small Travel agency. I need one logic to route the customer que over all sales agent so anyone once free he will be buzzup to pickup the customer till here is Okay. But i need some timeout if no sales agent pickup the Que it will forward to the supervisor. Now here is my Question should i make a small desktop application and run in server to moinitor the time and forward the task.... or Is Web Service is suitable for this? (Forward means just it will update one field of table so it will start displaying in Supervisor screen.)
Is there a way to make a desktop application easily interfaceable via Web ? Meaning, can you have a way to interface with a single desktop application as if you were remote desktop'd into the machine but not? I am looking at doing this in ASP.NET or Silverlight.
I am trying to develop a web application(Using ASP.NET and c#) that uses a specific database hosted on web server. I will have another desktop application that will use a local database. Both databases have same structure and data at start up. Then databases will change when users add data to web application and an employee adds data to the desktop application. After a while I have to sync both databases.
What will be best way to do this? Is there any opensource example/ starter kit to start with?