I have recently migrated my old XPages application to HCL Domino 12. I have also upgraded my dev environment to the same version. Unfortunately I am not able to compile the project since then. The process got stuck when it tries to invoke XSP builder as shown in the picture. Has anybody same/similar experience?
Google search did not show anything related.
Related
Domino API is not available to be checked in the xpage properties of my databases
I am trying to use domino api to help with some of the recycling problems that we've had with xpages. I've spent days watching the various videos that have been made over the years. I have tried to get this working in both my work environment (9.0.1) and my home dev server (10). In both cases the result is the same - I have installed the extension library and domino api on the server via updatesite and it seems to be fine there. In my designer I can see that both extension library and domino api are installed (by looking in Application Management) but only extension library is available in the databases.
Need to be able to select the org.opentf library in the datbases.
We've tried to clarify in the release page. 4.2.x is for 9.0.1 FP9. Since 10 we've moved to updated version numbering, although Tycho doesn't make it straightforward. So 10.0.0 covers V10. The version in Notes needs to match the Notes version, not the Domino version. It's referenced for compiling only, not pulled into the design. So on the server, the version needs to match the Domino server version. So you may have different versions if DDE and the server are different. That's to do with how OSGi works.
Scripting in VS 2015 for Unity 5.5.2 project, needing to upgrade to C# v.6+
I have VS community 2015 version 14 update 3. I am working in Unity 5.5.2 and trying to learn the game engine. I am trying to create some scripts which opens up into VS. Upon trying to add default initializers for properties of my class it gives an error. For some reason the program loads using C# version 4.
I would like to upgrade this to version 6, but when I have read other solutions to change the C# version it has always been going to the projects property page.
Snesh Prajapati's example doesn't work as the property page didn't have those options.
After trying David De Sloovere's solution some reason (maybe being a Unity project) the screen just flashes and no page is loaded when I try to bring up the projects property page. I even went and deleted the project.config file that was created, to not luck to get the properties page back displaying.
You are out of luck here. Unity uses an older version of C# (4.4 as of Unity 5.5).
To see the exact version of C# you are using, run the line Debug.Log(System.Enviroment.Version); and check your log.
I have just upgraded myself to new version and started development in 9.0.1 Revision 20131022.0932 ( release 9.0.1). I have couple of small queries.
1) Am I using the right version for development or need to upgrade by implementing patches etc?. This is stable for development?
2) Previously I was developing applications on 8.5.2 but my clients were on 8.5.x and 9.x.
This migration is safe for existing applications? no crashes? no code mismatch? Is their any guideline for developer? Co-Existence of clients is possible?
Please guide me and thanks in advance
Best Regards,
Qaiser
In general, upgrading to the latest Designer version is ideal, especially with (as Per recommends) the latest fix packs, as well as on the server.
For non-XPage design elements, there should be no incompatibilities with 8.5.x through 9.0.1, so you're good there.
If you do XPages intended to be rendered by older versions (either older servers or XPiNC in older clients), you could run into trouble there, using properties and controls that don't exist there. You can mitigate that a bit by going to the app's "Xsp Properties" in Designer and changing the "Minimum Supported Release". That won't help you avoid trouble with third-party plugins not installed everywhere, but it helps with the core runtime controls.
We have just upgraded to VS2012 from VS2010. However, any form with a chart control on it will not load in the designer (although it compiles and runs OK). We are using the .Net 3.5 version of MSCharts and cannot go to .Net 4.0.
We are getting errors like:
Could not find type 'System.Windows.Forms.DataVisualization.Charting.ChartArea'. Please make sure that the assembly that contains this type is referenced. If this type is a part of your development project, make sure that the project has been successfully built using settings for your current platform or Any CPU.
The chart control works fine in VS2010, and I have double checked that we have the correct dll referenced, so this looks a lot like a bug in VS2012.
Does anyone know if there is a patch/service pack for this bug?
If not, has anybody figured out a workaround?
I have installed the Netbeans 6.7 IDE with Java ME included, but cannot create a Mobile Application project from the Java ME category. When I select the project type the wizard stops at "Finding Feature" with the message:
Not all requested modules can be enabled:
[StandardModule:org.netbeans.modules.mobility.end2end.kig jarFile:C:\Program Files\NetBeans 6.7\mobility8\modules\org-netbeans-modules-mobility-end2end-kit.jar.
I am attempting to run this on Vista Home Premium. I have tried to run the IDE as Administrator with no luck.
I am at a loss for where to go next as I cannot seem to find any information regarding this issue. Even if you don't have the solution any insight into this error message would be helpful.
I am unable so far to get the project running via the Netbeans IDE install. I have, for the time being, installed the Java ME SDK which includes a very stripped down version of the Netbeans IDE for mobile development.
I originally had some issues starting the SDK as well on Vista. The IDE reported that it could not connect to the device manager on localhost. After some searching I found this link: Java ME SDK Startup Problem which suggests changing the hosts file localhost entry from IPv6 to IPv4. The fix worked perfectly and I can now compile and run code in the emulator.
This is not an optimal solution as the SDK does not include the visual design tools, however I am able to get a basic project going in the mean time.
I have given up on the 6.7 version and have instead located and installed 6.5.1. This previous version has been working just fine and seems to do everything I need.
I ran into the exact same error today while installing NB 6.8 beta. To resolve it we need to install two plugins:
Java Web Applications (as mentioned by Ali above) and
Sun Java System Web Server 7.0
Note that these two are part of the Category called "Java Web and EE" hence the confusion that we need to install Glassfish App Server. But we need these two plugins because they are required for debugging using breakpoints in emulator. Netbeans runs a web server when we do breakpoint based debugging.
Also note that the Java Web applications needs SOAP Web Services and JavaScript Debugger plugins to run and so these plugins are also installed when you try to install it.
You also need to install "Java Web Applications" plugin.
Tools->Plugins->Available Plugins
If the module is present, you should try unzipping it to check its content makes sense.
You should also be able to rebuild it from Netbeans sources.
You can also try to figure out why this happens by debugging the module loader inside Netbeans from its sources, using another IDE, presumably the latest version of Netbeans you can find without the issue.
If the module is missing, you might want to get the missing jar file from an installation of a previous version of Netbeans, see if it is compatible.
6.5.1 isn't missing any module.
back in version 5.5, the mobility module had to be downloaded and installed separately from the main IDE.
If you want to consider using Eclipse for developing your J2ME app...I've written a post related to that some time ago: here.