Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a user control (UserControl1.ascx) and I made changes to its .cs file.
That UserControl1.ascx is being used by two or more aspx files using LoadControl.
I don’t want to deploy the whole web project DLL, as this is a fix for a critical issue in one part of the web app, and doesn’t affect the whole web app.
Updating changes to the single web form code behind is easily done. However I’m not sure about the single user control deployment.
It’s a bit of a hack, but you could move the code from the .ascx.cs file to the .ascx file and remove the
inheritsattribute. ASP.NET first checks the referenced class in theinheritattribute. So I think this should allow you to update the web application without updating the .dll files.I didn’t test this, but I think it could be a viable option.