npm mssql package intellisense not working when im offline? - npm

I'm currently working on a nodejs project in an offline domain and came across this issue that I cant seem to find anything about.
Apparently even after installing the mssql package in visual studio code, intellisense only works when i have network.
if that helps, I installed the package from an online computer and then moved it to the offline computer, but the same problem shows even if i just unplug my computer and reopen vscode.
its also worth mentioning that packages like express and morgan does have intellisense even when offline.
Is there an option to also save the package's intellisense locally?
thanks!
mssql package: https://www.npmjs.com/package/mssql

So as it turns out, and even though I checked multiple times if it's network related or not, the problem were with some settings that I set up 2 years ago when I were coding with powershell.
Removing it worked, so always take a look at the vscode settings (suggestions/intellisense categories)

Related

Trying to install React in Visual studio code?

I am just learning react now. I tried to install react app so many times in my Visual studio but It didn't work. It always shows installing required packages and I've waited so many hours with so many tries it didn't worked as well. I have this issue only and Node install 'my-app' folder with simple json file only. Anyone knows what's the problem here?
enter image description here
I tried to update Node recent version but it was already updated. Even i tried Non LTS supoert Node version it couldn't helped me.
I tried different types of package manager like 'npm' and 'yarn' instead of using 'npx' but then I know these package managers supported before node version 5.2 or 5.8, I think.
I searched for this problem in youtube nothing else there.
I used metered network in my PC but when I used WiFi with stable connection also it didn't install.
I tried so many different extensions in Visual studio, I thought it would be help but none happened.
What are the problems here? and What i want to do pls explain to me, bros.

VSCode Java Extension Pack: sudden linter, refactoring, semantic highlighting issues

Don't know how to go about describing the details of my problem, but out of nowhere all of the useful code tools that I use for Java have partially stopped working. Go To Definition, Change All Occurences, and hover functionalities have all disappeared. I'm working on a remote machine through SSH, but I don't think that's the problem because another computer I'm working on works fine.
I've tried uninstalling and reinstalling every extension I have, I've tried quitting and restarting VSCode, I've tried deleting and reinstalling the application, all to no avail. I'm desperately in need of help with this problem
Finally figured it out -- I had to start the RedHat language server extension from a clean slate with the command Java: Clean Java Language Server Workspace

Failure installing SQL Server 2008 R2 Express X64

I am having a serious problem installing this (from web platform installer and from the downloaded installer). I have a laptop with win7 x64 enterprise on it.
I have read the forums and tried all the solutions I have found, from permissions, .NET framework to copying the setup files etc. These did help move the install on but in the end it always fails for the database. I have tried following MS advice on trying to read the log files to see where it fails which is why I looked at some of the solutions but the fixes didn't work. What makes it worse is the solutions for retrying the install (removal of things from the registry) has made things worse on the laptop as other stings stop working every time I remove the SQL keys.
I was hoping someone here could look over the logs to see if they could give me a better indication of whats wrong. Problem is I can't see a way of attaching a zip file here

Your developer license has expired (Windows 8)

My temporary developer license (using Visual Studio 2011 Beta and Windows 8 Consumer Preview) expired and a popup asked me to aply for a new one. This all seemed to work, but when I build and deploy to the local machine it takes me to the app store and tells me that the developer license has expired.
I've tried:
Unistalling my app from the home screen
Cleaning my project solution
Removing my developer license using powershell command Unregister-WindowsDeveloperLicense and getting new license again
Restarting machine
I can create new projects that build and deploy fine, but my existing project is stuffed. Is the old licence cached somewhere and how can I get it to forget about it.
There is this similar quesion on MSDN. Someone managed to solve it, but there solution has not worked for me and there are other people saying it hasn't worked for them.
The first month this happened to me, a reboot solved it. The second time it didn't. I went into my package manifest and changed the package ID. It looked like a GUID and I just put kmg on the end. Then everything worked fine. Later I tried changing it back but it failed again so I guess my package ID ends in kmg now :-)
I believe it's because you're trying to overwrite a package that was shipped by a "different developer". They're going to have to fix that somehow but hey, this is what betas ^H^H^H^H^H previews are for, right?

ClickOnce Application Not Opening

I have a VB.NET ClickOnce application that I am trying to install on my computer. Previously, I was able to install and run these apps without issue. Now when I install the application, I can see the flash of a window opening, and then nothing. (There are also no processes left hanging or anything when viewed with the task manager.)
After some digging around I noticed that there are files in my Temporary Internet Files with names like "FusionBindError" and then my application name and different DLL names.
I have done everything I can find on the net to do, reinstall applications, reinstalled the .NET Framework, deleted my Local Settings folder and relogged in.
Does anyone out there have any other ideas for me to try?
I tried the Mage.exe suggestion, but it failed to help. Same with the other installation location suggestion. The application flashes at the bottom of the screen but does not open. I have tried using FUSLOGVW to check the bindings and nothing shows up in there. (Good or bad, there are no binding entries.)
Have you tried using mage.exe? This is a command-line tool that comes with .NET framework. Start up a VS command prompt, and try mage -cc. This will clear your applicaiton cache and will force a new click-once download. This is the first thing I do when my click-once applications fail and it works 99% of the time.
A couple of suggestions:
FusLogVW isn't working for you because you have to enable assembly binding failure logging inside the registry. This MSDN article describes how to do this.
Another thing that comes to mind is, perhaps the ClickOnce app install, or perhaps the whole ClickOnce store is corrupted. Try deleting the ClickOnce app store then reinstalling the application.
It's possible that new prerequisites were added that you don't have on hand. If the URL you are using points directly to "my.application" or whatever your equivalent is, prerequisites won't be processed.
So try pointing to the setup.exe that is created in the same directory as the .application file.
Other than that, it sounds like you're doing all the right stuff...
Also, it could be useful to run the fuslogvw utility on a machine where the application actually works. Or reflector.
And then see if indeed any of its dependencies being loaded surprise you.
Also, for these types of errors, be sure to check if disabling the antivirus resident protection helps. Sometimes it causes problems accessing assemblies' manifests and such.
I uninstalled my Kensington Mouse software, and that resolved my installation errors.
Who knew that mouse software that I never used could cause so much trouble??
Sometimes if your machine is working for days this problem will show up. Try to restart your machine. The same problem happened to me and it disappeared when I restarted my machine.