After the XE12 update, are any of you having trouble running the sample projects (compass, stopwatch, timer)?
When I try to run them, the programs just say "(program name) has stopped".
Have you updated your code to the latest versions? XE12 had a number of breaking API changes (such as renamed methods and classes).
You should make sure that the APKs that you've built are from the latest source, either in the add-on's samples directory or from Github, and the reinstall them.
Related
I had developed a VSTO module to Outlook using VB.NET and VS2017-Community.
At the first installation, it asked for an user authorization to install, showing the Product name and the Vendor/Manufacturer data, based on the ClickOnce compilation (I guess).
Everything rans ok...
But now I uninstalled completely this AddIn and, when I call the SETUP again (due to a newer version), the Outlook does not show this window anymore - the Ribbon is updated automatically, my custom ribbon appears, etc.
In other words: my new version is installed into Outlook seemless and runs perfectly; except for the fact of the VSTO window does not appear anymore during the Outlook load (which would be like I saw before at the 1.0.0 version of my software).
I would like to see a CLEAN installation, I mean, exactly what a user which had never installed my software would see.
Some data to enlight the problem:
1- I'm using MSI installation and uninstall. Everything runs 100%.
2- The uninstall clears all the registry keys and the application folder.
3- I saw %User%/AppData/Local/Apps/2.0 folder and, also, there are no references to my project.
4- I open REGEDIT and check the following keys. All of them are cleared (no references to my AddIn):
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Resiliency\AddinList
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\DisabledItems
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\CrashingAddinList
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\DoNotDisableAddinList
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\NotificationReminderAddinData
(there are no Local_Machine key created here, my Office is 32-bit not running as Admin/Local_Machine).
So, how can I make a clean installation like I saw before?
I appreciate any help.
I found the solution!
We must clean the references also in:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\AddInLoadTimes
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSTO\SolutionMetadata
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSTO\Security\Inclusion (keys and subkeys)
That's it! :)
For last two weeks I was trying to build SOFA framework and run some examples, with haptics force feedback, from this directory ../plugins/Sensable/examples/Denistry/.
But unfortunately I can not succeed to run it properly, because runSofa.exe stops running, when I open any of those .scn files from the directory mentioned above. I followed all the instructions to build and run from official site (https://www.sofa-framework.org/community/doc)
What I did is :
downloaded 16.08 branch sources from https://github.com/sofa-framework/sofa
configured and generated Visual Studio win32 project by CMake
built release sofaRun and sensable plugin
errors occurred in senable project, especially NewOmniDriver.cpp and OmniDrivver.cpp files. I added sofa::helper namespace [adding_sofa_helper][1]
then it compiled without errors
I am hoping to find anyone who was able to run or build simulations with haptics force feedback and want to understand what I am doing wrong. If you need more explanation about what exactly I did, I will provide it. I will appreciate any response related to this topic.
I have succeed on running examples with haptic feedback using sensable plugin. The sofa developers are still updating the sources of the framework. So I checked the master branch of their repository and build that sources. After that the examples with haptic feedback worked as it suppose to do. – Ruslan Rakhmatov just now
I am new to sonar, i have installed sonarqube on RHEL 7 machine and its version is 5.1.1.
and the runner's version is 2.4.
I have four cpp related plugins, i tried with each one,
sonar-cxx-plugin-0.9.4-RC3.jar sslr-cxx-toolkit-0.9.4-RC3.jar
sonar-cpp-plugin-3.6.jar sonar-cpp-plugin-3.5.jar
sonar-cxx-plugin-0.9.jar
nothing seems to be listing the Sensor CxxCppCheckSensor . i need this for integrating cppcheck with the sonar. my cppcheck version is 1.68.
i have included sonar.cfamily.cppcheck.reportPath = in my sonar.project.properties file too.
Am I doing something wrong here ? Please help me out.
1.And do these cpp plugins needs license or trial key for proceeding?
2. Can cppcheck's xml report alone be viewed in sonar's dashboard?
Thanks in advance :)
sonar-cpp-plugin correspond to the commercial plugin and of course needs a license, sonar.cfamily.cppcheck.reportPath property is only for the commercial plugin.
sonar-cxx-plugin correspond to the community C++ plugin and has different properties.
Do not mix the two different plugins and documentation, pick one and follow one documentation installing only one of them.
Today after updating our projects it seems Xunit.KRunner is no longer available on NuGet. We checked the Microsoft projects and it looks like they are using the xunit.runner.kre package. When trying to install this the xunit.assert assemly is failing to download from Nuget. Any suggestions to get this working? I am guessing that the versions are messed up.
Here are my nuget package locations:
I'm also using the beta2 version of the kre.
There is/was an issue with the new xunit.runner.kre and VS CTP 5. See below discussion:
https://github.com/aspnet/Testing/issues/65
xunit.runner.xre is available only on myget/vnext feed. Include that in the Nuget.config that you should be able to restore the package
By running on the beta2 kre you're then having mismatched dependencies. If you look at the versions of your xunit bits they're all beta3. I'd recommend upping your kre to beta3 to fix your issue (will affect which packages your app pulls in).
Also as a side note I'd recommend ensuring your nuget.org/api/v2/ feed is enabled (in the SS you posted it wasn't). There's currently an issue where it'll occasionally disable itself; has definitely made my life frustrating several times when things don't build :).
I have a Glass GDK app (open-source on Github) that works fine on XE12.
I got the XE16 update yesterday, and now when I run gradlew installDebug to deploy to Glass, I get the message:
:onebusaway-android:installDebug
pkg: /data/local/tmp/onebusaway-android-debug-unaligned.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Here are the changes I've made to update to XE16:
I've changed my compileSdkVersion to "Google Inc.:Glass Development Kit Preview:19"
I've updated the gdk.jar in the /libs folder to the file from <android-sdk>/add-ons/addon-google_gdk-google-19/libs
Added <uses-permission android:name="com.google.android.glass.permission.DEVELOPMENT"/> to manifest for pre-production voice commands
(I actually made these changes prior to receiving the XE16 update myself, based on reports of it failing on XE16 from others - so I can confirm that with the above changes the app still works fine on XE12).
I'm using this third-party progress bar library, but from what I can tell from the release notes nothing has changed with the GestureDetector or Gesture Glass classes, which are the only Glass-specific classes it relies on.
My Glassware is an immersive Activity, so I'm not relying on TimelineManager or Cards (which changed in XE16).
EDIT
I've tried removing the third-party progress bar, but that doesn't seem to have any affect - still the same error.
I've also updated to Android Studio 0.5.5, no luck deploying from there either (as opposed to running gradlew installDebug from command-line). Also tried removing /libs/gdk.jar since this isn't required in Android Studio 0.5.5, still no change.
If you have any <uses-library> elements that aren't supported by Glass in your AndroidManifest.xml, you must include the android:required="false" attribute, or remove the element completely, for your app to install on XE16. This is a change in behavior from XE12.
According to the Android docs:
If <uses-library> element is present and its android:required attribute is set to true, the PackageManager framework won't let the user install the application unless the library is present on the user's device...The default android:required value is "true".
I borrowed code from a normal Android app for my Glass app, and I had a leftover element buried in the manifest:
<uses-library android:name="com.google.android.maps"/>
Since I didn't include the android:required="false", XE 16 is correctly preventing the app from installing.
Apparently XE12 didn't enforce this, and installed the app anyway.
After either adding the android:required="false"attribute:
<uses-library android:name="com.google.android.maps"
android:required="false"/>
...or removing this <uses-library> element completely, the app now installs correctly on XE16.