I can use ethereum in my browser.screenshot in browser
but I can't use it in Visual Studio Code.screenshot of VScode
How can I solve this problems?
Related
I'm familiar with coding as far as setting up homebrew for classic consoles. I can read it. Pray writing it.
So what I want to do is compile some code from dapp university. I installed Gitsavvy, solc, cmake, visual studio 2019 because m$ is hiding 2017, and the other necessary installs. I followed a guide from medium.com
Sublime text is now aware of the Ethereum syntax Solidity and Vyper but it does not ever have a build system. How do you fix "No Build System" in Sublime Text for a solidity environment?
Thank You
I just installed WiX on my machine and then installed the extension for Visual Studio 2017. When I attempt to build the Product.wxs I get "Could not find wix.targets at ''" back. I can run a build from the command line using candle and light, but I need to be able to do this with VS. Is there a place I can configure Visual Studio to look for the wix.targets file. I'm guessing that is the problem since it looking at '' for the file.
Create a WiX v3 project not v4.
(This is not a duplicate of Print and/or modify the c# version that the razor compiler service uses to compile cshtml because I'm using RazorGenerator, not ASP.NET, the translation from .cshtml to .cs happens every time I press the Save button in Visual Studio, so adding assembly references or NuGet packages to my project won't help)
I have a C# Class Library project using RazorGenerator (a Visual Studio extension that transpiles .cshtml to .cs sources). RazorGenerator itself works fine and my .cshtml files are converted to cs correctly without any problems considering I'm using C# 7.3 language features and types defined in custom assemblies.
The problem is Visual Studio's own .cshtml designer (independent of RazorGenerator) seems to default to the C# 4.0 compiler version and doesn't even load System.Core.dll - so when viewing .cshtml files in the Visual Studio editor I get peppered with error messages that shouldn't be there:
"Feature 'out variable declaration' is not available in C# 4. Please use language version 7.0 or greater."
and broken namespace imports because it isn't loading assemblies:
I saw these SO posts:
Where to configure Razor page language version to C# 6?
C# 6.0 Features Not Working with Visual Studio 2015
...which suggest adding the NuGet Microsoft.CodeDom.Providers.DotNetCompilerPlatform package to the project and restarting Visual Studio, however that did not solve the issue.
I'm not very impressed with Visual Studio Express 2013, which is the free version of Visual Studio. I would greatly prefer to just compile my C# program form the command line. I've located the compiler csc.exe and I located the DLL files for .NET, but how can I compile a XAML file?
You want to use MSBuild (MSDN). This is the standard way to compile .NET projects from command line. This is also the compiler that Visual Studio uses internally. You have to have a .csproj/.sln file for it to work, but it will be the fastest and most effective way to get to where it sounds like you want to be.
You're looking for MSBuild. Visual Studio projects are XML scripts for MSBuild. To build a project or solution, you can use the following commands:
MSBuild MyApp.sln
MSBuild MyApp.csproj
Building XAML files is far from trivial and C# compiler isn't enough for this. The most recent MSBuild targets for XAML is in the C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Xaml.targets file. But doing all this manually isn't the best idea, you'll just overcomplicate things even if you manage to do everything without MSBuild.
I receive the following error on the Windows App Certification Kit for Windows 8.1.
The app manifest test detected the following errors:XXX takes a
dependency on Microsoft Visual C++ Runtime Package
(Microsoft.VCLibs.110.00) framework but is missing the framework
dependency declaration in the manifest.
My solution builds with zero errors. However, I receive an error after I create an app package and run the Windows Application Certification Kit.
I have added and removed references to the C++ runtime extension.
In addition, I do not see any fields in the app manifest editor to modify that would resolve this dependency error.
It sounds like you are including a library that was built with Visual Studio 2012. You will need to rebuild that library in Visual Studio 2013. If you just have the binary you will need to get an updated version from the author.
..
Or
Rename "Microsoft.VCLibs.110" to Name="Microsoft.VCLibs.110.00",
Or
Add a reference in your project to Microsoft Visual C++ Runtime Package
Add reference and find this Package. Adding this should resolve your problem