Your feedback is critical to help us make Visual Studio the best tool it can be! Productivity As always lot of these features come straight from your feedback and suggestions. This blog covers several of the top new features in Visual Studio 17.5-to see some in action, watch the Visual Studio 17.5 release video. Visual Studio has improved the cross-platform development experience with a new remote file explorer, Linux Console output to the Integrated Terminal window, dev container improvements, and more.īeyond individuals, Visual Studio also has new features to better support dev teams at scale, with exportable configuration files and a persistent update toggle helping ensure everyone on your team is working from the latest version of the tool. Game developers can now view properties from base classes modified in an Unreal Blueprint asset without leaving the IDE. We’ve also made it easier than ever to deploy your ASP.NET apps to containers. http/.rest files make it easier to test and iterate on your APIs directly in Visual Studio, while improved Dev Tunnels help streamline the configuration and management of your webhooks. NET and cloud developers, we’ve focused on improving the inner-loop dev experience.
If you are using MacOS or Linux, running the following command in the terminal will do the trick (it switches to the build tools directory and then moves the d8 to dx and d8.jar to dx.jar): cd ~/Library/Android/sdk/build-tools/31.0.0 & mv d8 dx & cd lib & mv d8.jar dx.For. You can do this manually or with the command prompt, to create the symlink for dx.bat (remember to replace the SDK directory with yours): mklink C:\Users\username\AppData\Local\Android\Sdk\build-tools\31.0.0\dx.bat C:\Users\username\AppData\Local\Android\Sdk\build-tools\31.0.0\d8.batĪnd the command to create the symlink for dx.jar: mklink C:\Users\username\AppData\Local\Android\Sdk\build-tools\31.0.0\lib\dx.jar C:\Users\username\AppData\Local\Android\Sdk\build-tools\31.0.0\lib\d8.jarĪfter copying and renaming the mentioned files or running the previous commands to create the symbolic links (shortcuts), you will have new 2 files in the build-tools and build-tools/lib directory: This will work in all the operative systems, however the way to do it will depend of every platform. So the workaround to prevent this exception from appearing is either to copy the mentioned files that exist with the new names or create a symbolic link (shortcut in Windows) and it will magically work. These files exist however with another name, specifically:
The cause of the corruption of the build tools for API 31 is 2 missing files: Fortunately, there's a way to make the build tools work for API 31. In many blogs, you will find that the solution is to downgrade to the API 30, however, if you want to experiment with the API 31, downgrading isn't a real solution.
0 kommentar(er)
