Geek Answers Handbook

Error in .net Project & Designer file properties blocked

The constructor file is locked, and when passing to the project properties, it gives this error.

An error occurred while loading the project properties window. Close the window and try again. The CurrentContext LicenseManager property is currently locked and cannot be changed.

.net framework 3.5 VS 2008

+6
c # visual-studio-2008 projects-and-solutions
source share
6 answers

Just a random suggestion:

Close VS, then try deleting the .suo or .csproj.user files. These repositories are on user settings, such as files that you have opened, etc., and can sometimes be damaged. (maybe back them up just in case first)

+5
source share

I agree with Simon. I received this error and could not solve it. I deleted all unused links from the mysoftware properties in the project menu and then deleted the unused database. he solved my problem. I am sure this will work for you.

Sometimes some corrupted files cause this problem, although you have never used or relied on licensing your software.

Njoy ..

SandeepV

Adobe Certified Expert

Microsoft Certified IT Specialist

+1
source share

Some resources that you use in your project are compiled with different versions of the .net framework.

Right-click on your project, select properties and change the target structure to the structure that resources are compiled or removed from these resources and continue.

+1
source share

This occurs when constructor codes access the true Application.DoEvents infinite loop in the constructor button / dropdown / control.

You can see that VS.net occupies one processor core, and you can easily debug it using another instance of Visual Studio.

0
source share

If you get this error when opening a form design (and not an xml type), you can close the form, open the project property, select the build tab, click on the .net framework version, and you can select the same version again, close the project property, open it again form. that, as I got rid of the error, closing the visual studio and reopening the project did not help me

0
source share

More articles:


All Articles