Alright, here's hopefully my last question about a problem I'm having with my Adalight setup. Anyway, Processing exports two folders, application.windows32, and application.widows64, both of them have a adalight.exe file inside of them, along with lib, and source folders. When I try to run the adalight.exe file, nothing happens, nothing loads, no windows show up, there's no error message. I don't know if it's a problem with my PC, the Processing IDE, or my code (works perfectly if ran through the IDE). I'm not sure if this is enough information, if you need any more I'd be happy to try to provide as much as I can.
Related
Could not load file or assembly
'Microsoft.Cis.Monitoring.ConfigReader.DLL' or one of its
dependencies.
I'm running an Azure based web application at a large company.
I've tried the fix of forcing 64bit IISExpress. But it still happens. There were no code changes AFAIK that got this to start happening.
I'm not sure how these binaries got there in the first place, but there were several dozen binaries not referenced anywhere in the code in the .BIN folder that shouldn't have been there at all. Renaming the bin folder and recompiling solved the problem. Simply deleting it of course would have worked but renaming it gave me better feedback on what was going on.
I have a several years old Mac project that I'm now doing maintenance using Xcode 4.5. I made some changes to the code and was testing the changes using the debugger. Every change I make is compiled as I see the relevant warnings and have had to fix errors along the way. But when it actually runs, although it shows the code up to date, the debugger is behaving as though the prior version of code is still there. It will line up with commented out code and execute that code as I step through. Changes I have made are completely ignored, and it seems like the compiled code being debugged is the old code and not the new code that I am working with.
BUT, when I run the actual build file from my build subfolder, it does indeed have the changes in it. Just can't debug it and need to in order to find an issue!
I am guessing that the derived data folder or the files that are used by the debugger are somehow out of sync or pointing to the wrong location. I tried deleting everything there and of course have run multiple Clean's on the code, to no avail. I've also tried switching between LLVM and GCC, and also the two debugger options in the edit scheme section.
Any ideas?
Has anyone ever encountered a situation where your assets (image png files) got deleted from your web path?
Let me explain it little more clearly.
I am loading some images located in my localhost (not in flex4 application path) from my flex4 application using the loader and also with BulkLoader
This is the second time it happened that some of the images got deleted from the path which are in localhost.
I am not sure what is causing this? is that the loader? or bulkloader or the webserver? (WAMP) or any virus?
It happened 2nd time in last 7 days. I was lucky that I had a copy in the remote host so I got them back easily. But its a mistrey what and why it is getting deleted.
Any thoughts what might have caused this? or anyone knows any bug in the Loader or BulkLoader?
Well I found the answer. The culprit is the Flash Builder.
I am prity sure many of flash developers have faced the debugger launching issue where the flash builder never launches the app as it might have struck up some where and it halts the launching process at around 50-60% progress. It happened to me too and happens considerable enough times in a day.
I just found that this is linked to the issue which I have asked.
FB cleans the debug/output folder every time the app is compiled. I wouldn't have mind if it cleans only the project files. However, it just removes all the contents in the folder and adds them back. This happens in the back ground every time I change the code and save and run or "Clean" the project to build a fresh copy.
During this process (removing and adding files back) if the FB struck up and I forcefully terminate the process (which is must some times); my files are gone.
The flash output folder is my web root where I will have all my php, assets and all server-side stuff.
I will open a topic to discuss on how to avoid it which also I have problem there too.
Opps: This is the same as: Is there a way to reset the error badges in Netbeans? but I don't know how to mark it as such ...
My version of NetBeans 6.9.1 is currently showing a large number of syntax errors in many files, in many projects.
But, if I look at the errors, they are invalid. For example, one error says that an import is referencing a non-existent file. However, that file exists and has no syntax errors.
More importantly, despite all of the errors, the code compiles cleanly and runs correctly.
My guess is that NetBeans is caching some data (OSGi?) that is out of date or has been corrupted. This has happened before, but in the past it wasn't this bad and it magically cleared itself.
I've tried starting and stopping NetBeans, but that doesn't do it. If, as in the above case, I use NetBeans to resave the imported file, it goes away after a minute, but for large projects this is very time-consuming. (Note that I am using jVi, and saving with that embedded editor doesn't not fix the problem, it has to be the NetBeans save command).
I'd really like to find a simple way just to force the whole internal state to refresh itself. Does anybody have any ideas?
To clear this error you need to shut netbeans, go to the .netbeans folder in your home directory C:\users\.netbeans for Win 7,
in there you will see a folder for the version you are using.
in there is a folder called var
delete this folder then re-run netbeans.
This clears the cache in Netbeans allowing it to re scan the folders correctly.
I found a useful plugin you can use called Cache Eraser.
I have no idea how this started so I'm guessing there's a setting somewhere that I've been unable to find. I have a test that calls a method but when I run debug, it simply will NOT step into that dll. At all. Period. Throws an exception just fine, but it's kind of worthless when I can't step into see what's actually going on.
When another team member picks it up, he's able to debug the exact method I was attempting to target. Yes, same breakpoints, yes, same code (I checked in, he got it, ran just fine)
What the hell?
update : checked the test project for stupid entires, deleted the debug/release folders for fun, I've went though and dumped the project completely and got it back out of tfs. I've nuked the appdata/local/ms/vs/10.0 folder and the /appdata/roaming/ms/vs/10.0 folder. Deleted the local test results.
You probably need to investigate your project references. Is the DLL possibly GAC'd? Take a close look at the *.csproj file.
The fact that it can be debugged no problem on someone else's machine indicates to me that you're having an environment issue. Some sort of multiple library reference issue.
Another possibility: Visual Studio (and all its embedded tools) can have many strange caching behaviors. You might want to clear out extraneous MSTest-related temporary cache files/dirs.
Ok, got it. You can't do one of those things and it works. I had to do them all prior to opening up vstudio again. It'll blow your settings away just as a heads up.
Kill the AppData/Local/Microsoft/visualstudio/10.0 folder
Kill the AppData/Roaming/Microsoft/visualstudio/10.0 folder
Kill your entire project ... all of it.
Get latest (force)
And it works again.