I have just installed the Visual Studio code and redhat.java (Language support for Java by RedHat). I have added a new folder to workspace which contains many project modules.
When I try to open a Java file from those folders, I see that the redhat.java extension starts and is stuck alwas at 37%.
I tried deleting the folder in the /workspaceStorage from the %appdata%\Code\User\workspaceStorage and restarted the system.
I have also tried reinstalling the extension.
But still, the problem persists.
P.S: I have no other extensions apart from this extension. This is the first extension that I am trying to install.
Related
I have converted a java jar file to a dll file using IKVM.
I have created a simple C# application in VS2015 that has the converted dll as a reference to it. I had installed IKVM package using the following command:
Install-Package IKVM -Version 8.1.5717
After the installation ended, my application has a list of IKVM dlls referenced to it.
I had created a setup project for this simple application using Visual Studio Setup project. After adding the Primary Output files and all the IKVM dlls to the setup, I am building the setup project and getting the following Microsoft Visual Studio 2005 window asking for vs_setup.msi file.
I found this file in 2 locations:
C:\Program Files (x86)\Microsoft Visual Studio 8\Microsoft Visual Studio 2005 Team Explorer - ENU\vs_setup.msi
"[DVD Drive]:\vss\vs_setup.msi"
When I am trying to point to those locations, I am getting the following window:
Why building the setup project in VS2015 required vs_setup.msi of VS2005?
How can I fix this issue in order to create the setup.exe file successfully?
Note: My OS is Windows 10
Update:
I have tried to reinstall Visual Studio 2005 SP1 but it didn't fix the issue
For some reason it seems that not all the features from your Visual Studio were installed to your system. This isn't a bug, it's just one of the ways that some features can be installed, as "run from the DVD" or "install on demand". When it asks for the MSI file it requires the exact same MSI file, which is internally identified with ProductCode and PackageCode guids, and if they don't match the requested MSI it won't be used. From that screen shot, it's clear that the Visual Studio Premier Partner Edition disk is required, not that Team Explorer MSI file.
Visual Studio setup projects aren't part of Visual Studio 2015 - there is an installer extension that needs to be installed separately, this thing:
https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2015InstallerProjects
I'll repeat that your comment saying it requires vs_setup.msi is not what the message actually says. It requires the install disk, and it's possible that with the Partner Edition Visual Studio the Installer Extension is on the disk, and that's why it wants the disk. The installer extension isn't installed, but it might be on that disk. If you haven't got that disk, try installing the Installer Extension from that link above.
We had someone develop an Android app for us and although I have all his project files I cannot seem to get rid of the many warnings and errors that appear after import his project.
I am not a Java programmer nor have I ever used Eclipse, so I'm running pretty blind here, but I need to fix a couple of bugs that I at least managed to find in the code.
The developer saved his workspace as well as the Eclipse exe and all the jar files in a folder structure. What I have tried to so far is:
Copied all his Windows folder structure onto my Windows machine
Opened up the Kepler Eclipse exe in this folder structure
Set the workspace to the existing "Workspace" folder in this structure
Updated a bunch of .jar paths that were showing up as errors from his paths to my new paths (this resolved those errors)
Installed API 19 in the SDK manager (and selectved it) in order to get rid of android-19 errors
Added the Workspace default JRE in the Java Build Path section as there was none there and to try and get rid of the "Build path specifies execution environment J2SE-1.4. There are no JREs installed in the workspace that are strictly compatible with this environment." warning that I suspect is related to the over 200 resolve type errors I am getting.
I've searched the forums to no avail. Any guidance would be appreciated.
Just installed Eclipse Luna on a new computer with Ubuntu 14.10.
Copied my workspace over.
My projects will not build. The Console continues to show "Java Problem."
For example one of the 500ish errors with Java Problem:
Animator cannot be resolved to a type DefaultClusterRenderer.java /library/src/com/google/maps/android/clustering/view line 882 Java Problem
And it says the same "Java Problem" for about 500 more lines.
I have:
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
as my java path and I also have a copy of the JRE folder with contents within the eclipse folder.
What am I leaving out? My projects were building fine on my old computer.
When importing a workspace into a new computer or version of Eclipse, make sure that your target build versions are the same as in your previous workspace. This project required the Google Play Services Library and a Google Maps Library. Both of which had been marked with a target build of a deprecated version of Android.
Right clicking properties on your project and then selecting Android will allow you to change the build target as needed.
I'm trying to make a cross-platform project using C++ on Windows and the Android NDK. I've been trying to put it together in one project with multiple build configurations, but I'm running into a problem for the Android build.
My project directory structure is as follows:
PROJECT/
src <- This has the Android SDK files
jni <- This has the Android NDK files
src-mp <- Multiplatform C++ code
src-pc <- Windows-specific code
gen
res
...
When building for Android, the src-pc folder contains code that doesn't compile and generates errors (it's using GLFW and GLEW, which doesn't seem to be compatible with Android). I right-clicked on it and hit
"Resource Configurations -> Exclude from Build".
However, the errors in src-pc are still being reported and so Eclipse refuses to run the application. I know the application runs on Android without the src-pc folder.
I suspect it's something with the indexer, but I can't get it to ignore the files in the src-pc folder. I've considered setting up a separate dependent project for Windows, but I was hoping that there was a way to put it all in one project. I've looked at the resource filters functionality, but I don't see a way to set filters for specific build configurations, so that doesn't help.
I already found that it's possible to delete the problem reports in the Problems tab, but doing that every time I build is a nuisance and I was hoping for a better fix.
I'm using Android NDK R9D and the SDK tools for API level 19. I'm on Eclipse Kepler. The toolchain being used for C++ compilation is Cygwin GCC with the Android Builder.
I implemented the current version of ActionBarSherlock to my Android Project.
Everything works fine and I don't get any errors.
But when I try to debug or export my project I don't get an .apk-file out of my project. Just a .jar-file with the name of my project.
I've read about some problems the SDK had with building projects that contain external libraries but this was at SDK version 14 and so I hope, this bug is fixed...
So there might be another cause for this problem.
Does anybody know a possible solution?
You cannot get *.jar file as the result of building Android project. This seems very strange to me. There must be something wrong with your project settings (if you changed them), or the project you build is of the wrong type (i.e. it is Java Application instead of Android Application).
You didn't mention which IDE do you use, but I assume you use Eclipse.
Make sure you have installed Android SDK and Eclipse ADT correctly (just in case).
Next thing to try is to create a new Android Application project from existing sources (there should be such option during the process of creation).