I run setup file from Releases, and tried to follow official guide, but it has instructions for older versions only (Visual C++ 2010/2012/2013). I didn't find menus mentioned there. So how do I install vld on VS 2019?
Just use fork of VLD by Azure instead. It supports last versions of Visual Studio without additional configuration and fixes some bugs:
Microsoft Fork
This fork was created to address some of the issues found in the original repo https://github.com/KindDragon/vld, which has not been updated since November 24, 2017. The changes in this repo can be merged back into the original repo if it is again accepting pull requests.
If you would like to contribute to this fork, please submit a pull request. It will be looked at on a "best effort" basis as our team is available.
Copied from README.md
Congratulations, now you can use VLD, just
#include <vld.h>
Related
Can anybody recommend a working Android Studio sample app that I can use for Oculus Quest 2, preferably with good documentation? I am looking for something I can build and run to start playing with their OpenXR Mobile SDK.
I am on an Intel Macbook Pro running macOS Big Sur, and I tried with the latest stable Android Studio release (Arctic Fox).
I have tried two different samples so far:
VrSamples/VrCubeworld_Framework - from the official Oculus docs:
Android Development Software Setup
Getting Started with Oculus Native Samples: Import Gradle Project
After following all the steps, I keep hitting this error:
NDK not configured. Download it with SDK manager. Preferred NDK version is '21.0.6113669'.
I'm convinced my NDK is installed:
I believe I've tried every workaround listed in the popular Stackoverflow question, and the linked Google issue.
hello_xr - a comment on the Oculus Forum links to this helpful blog post with more detailed instructions than the official Oculus docs. Unfortunately, after following those, I hit this build error:
C/C++: /Users/dj/Code/OpenXR-SDK-Source/src/CMakeLists.txt debug|armeabi-v7a : CMake Error at /Users/dj/Code/OpenXR-SDK-Source/src/version.cmake:25 (file):
file STRINGS file
"/Users/dj/Code/OpenXR-SDK-Source/src/include/openxr/openxr.h" cannot be read.
Call Stack (most recent call first):
CMakeLists.txt:318 (include)
There doesn't appear to be an include folder under src, and there is no openxr.h in the top level include/openxr folder.
UPDATE: At Jherico's suggestion, I downloaded Oculus OpenXR Mobile SDK v1.0.13 and OpenXR-SDK-Source release-1.0.13, and followed the instructions again to exactly match the versions used in the blog post, and ultimately I did get it working!
I created https://github.com/daj/OculusHelloXR to snapshot my working Android Studio project with all its dependencies, with individual commits for each step that I followed (I had to make a couple of changes to steps in the blog post to get it working).
I wrote everything up in this blog post: https://daj.medium.com/oculus-vr-for-android-developers-a38134c759b0
The blog post instructions are likely out of date, since they're from April and the most recent version of the OpenXR SDK has it's own new build.gradle file for hello_xr that was added in 1.0.20 in October.
If you want to go by the blog post, I'd suggest that after you check out the OpenXR-SDK-Source repository, you then run git checkout release-1.0.14 since that would be the version that the blog post was written against.
Alternatively, you can just ignore the blog post and try importing the build.gradle project directly into Android Studio (basically following the "Import Gradle Project" steps you linked to, but importing hello_xr from the current version of the OpenXR-SDK-Source project instead) and try seeing it that builds.
If you're still getting NDK errors you might try explicitly setting the ANDROID_NDK_ROOT environment variable, and make sure it's visible to your build process.
i tried to use VCS > Import into version control > Share project on GitHub. https://snipboard.io/aTBxe9.jpg
However i got an error https://snipboard.io/6Eashw.jpg . then i used https://stackoverflow.com/a/27701083/15334005 and followed all the steps yet none of my files appear on github.
https://snipboard.io/7sSbcq.jpg
i would share any further information required. if someone provide me an updated ist of instruction to be followed since both github and android studio have changed w.r.t previous answer i promise to update the steps for newer version and changes below this line as i learn to do it for use of future people.
Will update my answer as i learn and will keep this answer updated wrt newer version and changes for future users.
Is there a way or a tool to force users to write a comment to TFS every time a release of a project is created?
I am searching for something similar to the comments that are input when a file has been checked in to TFS, only for releases instead.
We are having a hard time keeping track of the changes made each time a new release is deployed and I imagine this would be a huge help in keeping track. I am currently using Visual Studio 2012.
What you're looking for is a release management solution, so you can automate and track your software as it's delivered through a pipeline from your dev environments up through to production environments.
You didn't specify what version of TFS you're using, but if you're using TFS 2013 or earlier, you can use the Release Management server. This software is being deprecated, however, so I wouldn't recommend starting out with it now unless you have absolutely no other choice.
In TFS 2015 Update 2, there is a fully integrated release management hub in TFS. This would be the recommended approach.
I recently acquired XMLSpy 2013 and was naturally excited to see there was a Visual Studio integration package. I'm running VS 2012, but nowhere on Altova's download page does it mention compatibility requirements/limitations.
So I followed the steps on the Altova download site (basically just run the package and you're done). Nothing changed in VS. So I decided to download the 1326 page PDF manual for XMLSpy to see if there was some extra help in there:
http://www.altova.com/documents/XMLSpyPro.pdf
On page 490, it mentions going into your VS/Common7/IDE directory and running devenv.exe /setup which I did. After that, again, nothing changed.
Has anyone had any success with getting this integration package to work? I can find almost no information by searching the web.
I actually created a support ticket with Altova for the issue as well, but thought I'd try here for some first hand experiences.
Whelp, Altova support responded to my ticket. The answer is, since Visual Studio is a 32-bit only application, XMLSpy integration will not work when running the 64-bit version of XMLSpy/XMLSpy integration package.
This is despite the fact that both a 64-bit version of XMLSpy AND a 64-bit version of the Visual Studio Integration package exist side-by-side on the download page (as of writing this answer). I have a feeling that it might only exist for the Eclipse integration.
http://www.altova.com/download/xmlspy.html
Once I installed the 32-bit versions of XMLSpy/Integration package, it all worked as promised. I hope this helps someone in the future at least.
For our latest release, we want our customers to only download an upgrade patch of our applications and instead of uninstall and re-install all the process will be done by upgrader patch but I know nothing about this even after I googled it! Where to start guys? Note that our new release includes database upgrade as well as production code!
We are using .NET 4.0, Visual Studio 2010, C# and VB.NET in our software.
I might be a bit late to the party but hopefully this post helps anybody else who is looking for this answer.
You can use the 'Patch Design' method to create patches. You can find it in Installation Designer tab under Media.
For this you will need the latest build (msi/exe) and one or more previous build(s). In 'Patch Design' add a new patch configuration. From there you can specify latest version and previous version(s) of your setup file. If you are using Express version then you will need uncompressed build for both latest and previous. If you have Professional version then it can decompress it for you.
After this, just hit Build Patch and it will create a update.exe with only differences between latest and previous builds. It is quite smart in a way where it will only add the binary differences.
Good luck.