VS Code, Windows, OneDrive, GoLive issues - visual-studio-code

Hello, I am new to VS Code, used Atom before. We were trying to use "GoLive" to view some html with javascript, and getting strange errors. It seemed like the errors had to do with the fact that files were being served from the user's OneDrive at some point, instead of from their hard drive, where we'd put them originally. I assume the solution is to un-sync the folder we're working and testing in from OneDrive?
Other folders (and projects) were working, so we tried renaming some folders in the VS Code Explorer, and at that point, we were not allowed to do so.
Any thoughts?

Unsynced oneDrive and restarted, and that fixed the problem.

Related

How to make custom changes to a VSCode extension directly from the extensions folder

Good day. I have a third-party VSCode extension that's been throwing an error all day. In order to actually diagnose this, and then submit an issue on the parent GitHub repository, I've been poking around and trying to figure out where the error is being thrown from.
I have a decent idea where the error is originating from, but I'd like to add a console.debug statements to confirm this.
My question is this: I've made changes to the actual VSCode extension source code (installed within the VSCode extensions folder ), but VSCode is not picking up those changes. What do I do? Clean the cache or something, I'm not quite sure.
The source file is basically just a Ts-compiled-to-JS file, so still pretty easy to work with.
I've checked out the Developer Tools Console (Ctrl+Shift+I), but the error stack is not particularly helpful.

Export to Java application deletes files

When I wanted to export the model I was working on as a Java application, I encountered an error regarding the databases I loaded into the model. When I said OK to the error, I realized that all the files in the folder I wanted to create the Java application were deleted. That folder was desktop by the way.
Right now all the files (i mean all of them!) on my desktop are deleted and they don't even show up in the recycle bin. How are we going to solve this situation? How can AnyLogic have the authority to delete all files in that folder? How is this authority not shared with me and not warned beforehand?
When you work with software in general, you need to have a version control in place that will allow you to recover your information. These problems occur, and if AnyLogic has access to your computer it's because you grant the permission and it needs the permission. If you make your desktop your project folder, then i would say you are to blame.. why would you do that...
Using GIT as Ben commented, is always a good idea... but it requires you to be conscious about when you commit a version.
What I do, is I use dropbox and all my projects are done in a dropbox folder... the good thing is that dropbox always saves automatically all the files on the folder... this has saved my life multiple times and I suggest you to do something like that in the future. So on one hand you have the autosaving features, which is useful, but sometimes you erase everything by mistake, and the autosave is not useful, but dropbox saves no matter what.

Prevent VS Code from opening all files in a folder recursively

I am currently using VS Code on a folder mounted through an SSHFS. The folder has subfolders with many jpg and other image files.
Logging all the files VS Code tries to open reveals it recursively touches all the files (doesn't read the content, just STATs them). This takes very, very long over an SSHfs mount and I can not cancel it without killing the editor (it won't even respond to regular closing).
During this, no files or directories can be opened (inside VSCode) and will show a loading spinner until VS Code has finally had it's way and checked all the files.
This behaviour only recently emerged, I can't pinpoint if any version beyond the current stable version has this behaviour.
I am thinking it might be the new searching engine, but I can't find out which part of the editor is doing it.
It looks like they just posted a fix for your situation:
Slow startup opening a large workspace over the network
you will need vscode v1.32.3

TYPO3 Backend Website-Panel is looking strange and is not usable

our BE-website-panel is looking kind of strange.
And we can't use the filter or add-new-element functions which are shown.
(We are clicking through to the sites themselves)
I didn't find anything regarding this bug so here's a screenshot:
backend
Also here's a list of the extensions:
extensions
I fixed the problem, altough i can't tell you where the error originated.
I downloaded the typo3_src-8.7.2 source files and overrode all my files via ftp, because i compared the whole folder with phpstorm beforehand and some files were empty on my side.

NetBeans: Code changes to javascript & css files are not reflected in browser after saving

This is driving me crazy. I'm developing an app in the NetBeans IDE in PHP, using the CodeIgnitor framework. I am making code changes to js and css files in NetBeans, saving them but the files the browser is loading do not contain the code changes. When I open the files directly outside of NetBeans, the saved changes aren't there.
I'm storing the javascript & css files in a folder called static, which is outside of the 'application' directory in CodeIgnitor. What's weird is any code changes in PHP files work fine. I'm guessing NetBeans is saving the changes to the js/css files somewhere else but can't find them on my hard drive. This just started happening, it was working 'normally' before.
Thanks for the help.
Al
I had the same problem, upon investigation, my browser cached my old style sheet that I had recently updated. Clearing the cache and refreshing showed my new styling, after around 20 minutes of frustration :D
This problem occurs due to browser cache. For chrome while testing open the developer mode by pressing the F12 key and set cache disabled in the network tab as shown in Image below. It will ensure that you will always get updated version of the page files.
Check to make sure that the files are where you think they are. I would imagine that CodeIgniter is rewriting the request to be inside your application folder and thus bypassing your specific folder.