This extension is broken for me. I already contacted the developer and the bug will be fixed upon it's next release. In the meantime, I'd really like to start learning DirectX (but I want to keep a safe distance from C++). Could anyone be so kind as to copy and paste the template the extension creates in it's whole? And also give me a list of the references it adds to the project. Thanks a lot. Sorry if the question is not well written, but I'm very ill at the moment. Thanks for any cooperation.
Related
I want to use Visual Studio Code as my editor for c # code in Unity and I want to hover over the code to display a short description of what, for example, the method does.
I found this thread but I don't know what to do exactly.
Does anyone know how to do it and is it such an option?
P.S.:
And by the way, does anyone know a good extension with syntax highlighting?
OK, I found something like an answer. I didn't think this would change anything, but I downloaded the Windows: .NET Framework 4.7.1 Developer Pack as this tutorial says and the syntax started to stand out and I get a little hint as I hover over the methods.
I was wondering how one would go about using Q# within Unity. I want to endow agents within a Unity simulation with quantum-like behavior, and I was wondering whether it was possible.
I've seen reference to adding a managed .dll in \Assets\Plugins and adding "using yourLibraryNameSpace;" at the top of scripts, but I'm not exactly sure whether/how that would work with the Microsoft Quantum Development Kit. I've attached some potentially related posts below for reference. Any information would be greatly appreciated. Thanks so much.
NuGet packages in Unity
Unity C# how to load a managed DLL properly?
Someone pinged me about this on Twitter, so I figured I'd put out the quick-and-dirty prototype I put together last year: https://github.com/amirebrahimi/qsharp-unity
So I'm making a small game for one of my last classes in university.
Basically I'm having some really awful issues trying to play a song in the title screen, then when the user clicks to start game, switching to a game play song.
The first 3 hours, I used the provided sound libraries, and then I ran into the issue many others have with massive lag to the game. So, I decided to give XACT 3 a try, the one packaged with XNA 4.0.
I made the project from scratch, in XACT 3, and XNA is telling me:
error : The .xap file was created with a version of XACT that is incompatible with the XNA Framework Content Pipeline version used by this project. Refer to the documentation for options to resolve this mismatch.
Now i'd love to refer to the non-existent documentation to find out they can't help, but can anyone out there please help me? I'm so close to being finished. My searches for the last few hours have shown me to clues..
After countless hours, it was of course something stupid.
When you load the XACT3 .XGS, .XSB, .XWB files into the solution explorer(Content in my case), you MUST also make sure to click on the properties of each one and make sure that Build Action is set to NONE.
The error was thrown because XNA didn't know how to build those files, and in true MS fashion, the errors are usually quite confusing and never really take you to the real problem.
Also, for future visitors, make sure you also set Copy to Output to ALWAYS.
I'm working on a visual studio 2010 extension and was wondering on how to obtain an existing language service ( the one for C# specifically ). All the articles I've seen on the web so far are about "Implementing your own language service", but I haven't been able to find any info on obtaining an M<existing one.
Just to provide some context here, the extension needs to open a custom wpf form on demand,in which i want to host a C# code editor window.
I'm not yet sure this is even possible, however any tips would be appreciated.
Well, it took me forever to word this question correctly, but I found a blog post answering the question on Google: Hosting the C# Code Editor in a Tool Window
I know it's kind of rude to just dump a link, but helpful nonetheless I hope.
One thing you can have a look at is the Roslyn CTP. I've seen a demo of it at the Dutch Tech Days last week and it looks quite nice.
It can help you in hosting your own coding environment and easily compile snippets. But it's still really beta and it doesn't support all the language features yet.
I started C# a while ago and really like it.
I work with VS 2008 and really like it.
I tried Resharper and loved it.
Now I am starting with Macros in VS2008 to increase my coding speed a little more. And stumble upon visual basic. And I do not like that.
Is there any way to write macros in C#. Or a workaround, in writing a plugin for VS to reach the same goal. Just let me stress out, its a productivity issue. I just want to automate some features I use often (create macro, assign shortcut, tell my touchscreen-app to send this shortcut)...
So from an experts point of view, is there an easy way to e.g. "collapse all items in the solution explorer, but expand all starting with the letter A" (just a silly example) without using visual basic?
Thanks for any tips,
Chris
PS: I was nearly happy with recording and playback. But, as it turns out, some "external" resharper command (like collapse all) do not play well with macros (getting strange com errors). So I thought, hey, a loop to collapse all items, I can do that. But unfortunately not really quick in VB :-)
Try writing a DLL in C# and referencing it in a VB macro.
This way, the only VB you'll need to write is the code to connect the DLL to the IDE.
Unfortunately no, Visual Studio only supports VB.NET for macros.
I wouldn't stress too much about not having C# for macros (many C# developers seem mortified that VB.NET code will stick to their shoe like toilet paper). Rather take pride in your ability to be productive in multiple languages!
Visual Commander (developed by me) lets you write Visual Studio 2010+ (macro) commands in C#.
Snippets are the closest which I've come across. Snippet Editor 2.1 does a pretty good job setting them up without to much hassle.