I’ve tried all the vb extensions and nothing appears to be working. Dotnet works on the terminal and other programs are working but not vb.net. Some say there’s no support but I was wondering if that is the case? Is there any extension that can run and debug vb.net on vscode?
Try the VS Code Extension Code Runner.
I had to add the path to vbc.exe to the path environment variable to make it work.
Related
Is it possible to show warnings (not used variables / typo), errors and an overview about my created variables and functions in an open file?
I have installed the newest Visual Studio Code IDE but if I press Ctrl + P and then !, my VSCode says there are no results. It doesn't know !-command and other commands I found in the internet.
What extension/addon do I have to install to see this? It would be great if I could see this in a separate window without using Ctrl + P and if the IDE would mark positions with warnings/errors in my open code as Eclipse-IDE can do.
Use Eslint. Install it globally using the following command
npm install -g eslint
It will show all possible warnings based on the rule sets given, while you are coding. Moreover VSCode is not an IDE it's just Code Editor like Sublime.
The main difference here is the word IDE...Eclipse is an IDE and is the most widely used Java IDE, but, Visual Studio Code is not an IDE, but, a code editor.
If you want to try a Microsoft IDE, you can download
Visual Studio Community, a fully-featured, extensible, free IDE for creating modern applications for Android, iOS, Windows, as well as web applications and cloud services https://www.visualstudio.com/vs/community/
Is it possible to show warnings (not used variables / typo), errors [...] in an open file?
The VS Code extension for quick-lint-js can show you syntax errors and misspelled variable names. It requires no configuration. (ESLint requires per-project configuration.)
At this moment, quick-lint-js doesn't tell you about unused variables.
Any ideas as to why MSBuild is always building all my platforms for my UWP solution even though I'm specifying to only build for the ARM platform. This is the command line I'm using:
MSBuild.exe C:\MyApp\MyApp.sln /p:Configuration=Release /p:Platform=ARM
Am I missing something or doing something wrong?
Thanks.
UPDATE - 1:
I've also tried specifying x86 as the platform, but it still builds all platforms.
After spending hours trying to figure out this problem, I have eventually figured out what's wrong, well partially at least!
As mentioned, the above does not work as expected, unless I first create a package via the .NET IDE and only select a single platform. Once I do this, the above command line will build the relevant platform that's specified in the command line!
I've just tried it again and created a package via the .NET IDE and re-selected all platforms and called my original command line once again, and it build all platforms rather than the one specified in the command line. There is obviously something in the solution file that's causing this but personally I think this behaviour is wrong and is a bug.
The following command lines seem to worked irrelevant of what has been selected via the .NET IDE:
To only build a package for ARM in Release mode:
msbuild "c:\myapp\myapp.sln" /p:configuration=release;platform=ARM;
AppxBundle=Always;AppxBundlePlatforms="ARM"
To only build a package for x86 in Debug mode:
msbuild "c:\myapp\myapp.sln" /p:configuration=debug;platform=x86;
AppxBundle=Always;AppxBundlePlatforms="x86"
While the above works, irrelevant of what's selected in the .NET IDE, I haven't figured out how to build all platforms.
I'll also investigate the original command line problem and the link with via the .NET IDE selection, and I'll update my answer if I find out what's causing it.
Hope this helps.
Is it possible to write an obj-C code with any text editor and then upload it to Mac server to compile it using Xcode??
I know that it is possible to compile your project using Xcode without open it something like use some command lines, but I am not sure is it possible to make it a server and then upload any obj-c code!
You can compile your projects from the command line using the xcodebuild command. Automating your builds is another story altogether: you'll need to set up your server to download the updated source code (typically via version control, e.g. svn update or p4 sync), do the build, and then upload the builds results somehwere (e.g. check into version control).
Doing this is non-trivial, and there's a lot of software out there, such as FinalBuilder, to help make this easier, although FinalBuilder is Windows software so probably isn't what you want.
I'm using Powerbuilder to call an external function from a DLL created in C#
If I generate an executable it works fine, it call the web service perfectly well, but when I'm trying to run it in "development" mode it don't use the "application_name.exe.config" file.
I tried to set "app.config" file hard coded in the DLL, but I was unsuccessful
Clues to resolve this issue?
I think you described it yourself: you're looking for it to use something used by the EXE when you're running from development mode. When you run from development mode, there is no EXE generated or used, so Windows won't be leveraging functionality linked to the EXE. (PB starts your application so quickly because it is only loading the application to the virtual machine and running its Open event.) If you need this, it sounds like you'll have to include Deploying of the EXE and running it as part of your testing cycle.
Good luck,
Terry.
When you compile and run from the exe you're using your exe. But when you run from the dev environment you're actually using pbxxx.exe (pb115.exe, pb110.exe etc.). You may be able to copy the "application_name.exe.config" into your pb directory and rename it something like pbxxx.exe.config. At least that's the way it works with manifest files -- I had two, one called appname.exe.manifest and one called pb115.exe.manifest.
Just curious but how many libraries/objects are in your application?
I have some very large applications and the longest any of them takes to do a full build is about 30 minutes. Something odd about your aapplication for it to take 2 hours to do a full build.
DLL's dont have config files. Only EXE's.
I'm not that up on VB.NET, the application I'm working on was not written by myself.
It works fine through the IDE but once I run it from the exe it gives me the above error.
Any clues?
This is really hacking me off!
The only user defined break point that I can think of is
Debugger.Break()
So, I would suspect that the .exe is compiled in debug mode. I would recommend Reflector to look at the code and find out for sure whether or not there is a Debugger.Break() somewhere in there.
Afaik, the only way this could occur if you are compiling under debugging settings. You should be able to fix it by doing the following:
Right-click your solution on the
solution explorer.
Select configuration properties.
At the top of the dialog box there should be a
combobox, which will most likely say
"Active(Debug)".
Click on the dropdown and select release.
Ok out of everything.
Build > Rebuild Solution.
Source: p2p.wrox.com
I believe the exe file was compiled using the "Debug" setting. Try changing the Build setting to Release and do a full build (rebuild) of the project. Then try to run the executable file. It should then run normally.
The reason you see that error is because when you normally compile and run applications in Visual Studio, it compiles a Debug build of the executable. The different between a debug build and a release build is that the debug build has additional information added to it, by the compiler, so it can be debugged properly.
I would suggest looking for stop in your code. That is what generated this error for me.