how to fix "Import "django.contrib.auth" could not be resolved from sourcePylance" in Django application development?

 when I try to import a library to the project. I spot a curly underline for the library that i just imported.

I hovered the mouse to the underneath, the warming message as following

    "Import "django.contrib.auth" could not be resolved from sourcePylance"

the root cause of this issue is related to the VS Code workspace configuration. we have to add this line to get ride of the error message.

{

    "python.pythonPath": "/venv/bin/python",

}

Since I did not have the .vscode folder when I setup my django project with command line window.

I have to manually create a .vscode folder under the project and add the settings.json file inside it.

I put the above setting in the settings.json file.  The warming message finally resolved.

update: if the above solution still doesn't work

you can change the python interpreter for the current project by doing the following

• use Ctrl-Shift-p to open command palette
• type python interpreter in the command palette
• select Enter interpreter path
• find the python.exe file under your venv\scripts folder

How to encrypt and decrypt configuration sections in app.config of window or console application with script

It is quite easy to encrypt web.config file in the web application. since Microsoft did provide us the tool (ASP.NET IIS Registration Tool (Aspnet_regiis.exe)) to get the job done.

you can simple run the following line in the CMD window to encrypt the connectionString sections in web.config file

I copied the below command line from MSDN Encrypting and Decrypting Configuration Sections

aspnet_regiis -pe "connectionStrings" -app "/SampleApplication" 

-prov "RsaProtectedConfigurationProvider"

the above commend line with encrypt the connection string section with RsaProtectedConfigurationProvider.

However the configuration file of window or console application is app.config. ASP.Net IIS Registration Tool will not work in this case. However there is  work around. we can simply rename the app.config to web.config file, then run the encrypt command. Finally we rename web.config file back to app.config.

 Script encrypt the app.config file

copy App.Config App.Config.Encrpytoriginal
rename App.config web.config
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -pef connectionStrings . -prov DataProtectionConfigurationProvider
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -pef appSettings . -prov DataProtectionConfigurationProvider
rename web.config App.config

Script to decrypt the app.config file

del App.Config.Decryptoriginal
copy App.Config App.Config.Decryptoriginal
rename App.config web.config
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -pdf connectionStrings . 
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -pdf appSettings . 
rename web.config App.config

you can save those scripts into two different batch files, and place them in your app project folder.

as a result, you can encrypt and decrypt in your configration section in the fly.