Copilot show only few row instead of complete code - github-copilot

I'm testing Github copilot on visual studio code, it work fine but with long code i have problem.
Also if i choose show on GitHub it not show the complete code but only a part of it
There is any method to see all the row of the code?```

Related

Small Basic - When would 'Graduate' be used?

So today I decided to take a look at the Graduate feature in small basic, I discovered that it allows you to convert your small basic code to a format for Visual Studio, Great I thought.
Until when I later tried it, Visual Studio reported that there were over 102 errors with the code, I found that this was because the compiler couldn't understand most of the small basic functions like GraphicsWindow, TextWindow, Mouse, Shapes etc. So, have I done wrong? As Visual Studio is my main programming language I couldn’t wait for the small basic code to be magically converted to work with VS. Some of the code could be manually translated such like TextWindow to Console, but what do you do with code that is specific to Small Basic like GraphicsWindow?
You are using the Graduate feature correctly, and you haven't done anything wrong; the reason you're getting errors is because Visual Studio doesn't seem to automatically import SmallBasicLibrary.dll correctly. The last time I used Graduate (~2 years ago) this wasn't a problem, so I imagine this issue is a result of Visual Studio updates.
Thankfully, this issue is easy to fix. You simply need to import SmallBasicLibrary.dll manually and then add a single line to the top of your Visual Basic code. Note that these instructions are for Visual Studio Community 2013, but I would imagine they're the same for most recent versions.
In Visual Studio, go to Project > [Project Name] Properties.
In the tab that opens, go to References on the side panel. Select SmallBasicLibrary in the list and click Remove.
Click the Add button (next to Remove), then in the window that opens select Browse in the side panel. Now click the Browse button at the bottom of the window.
Find SmallBasicLibrary.dll in your Small Basic installation folder (for me this was C:\Program Files (x86)\Microsoft\Small Basic) and double-click it. When you are taken back to the Reference Manager window, ensure that SmallBasicLibrary.dll has its checkbox checked, then click OK.
Select Application in the side panel and ensure that the targeted version of the .NET framework is 4.5.
Finally, open your Visual Basic code using the Solution Explorer and add this line to the top of it:
Imports Microsoft.SmallBasic.Library
The resulting code should look something like the following:
Imports Microsoft.SmallBasic.Library
Module UntitledModule
Sub Main()
TextWindow.WriteLine("Test")
TextWindow.Pause()
' Your Small Basic code here...
End Sub
End Module
All your build errors should be gone, as the Small Basic commands are now available.
Once you've done this, Graduate is ideal for using VB-exclusive commands or libraries along with your Small Basic code.

Export as Snippet menu option missing from Visual Studio 2010 Professional

I found these wonderful instructions on how to create your own code snippets in Visual Studio (after using them in Xcode, I have become addicted to snippets). However, when I go to follow the first steps, I select my snippet body code, and right-click, there is no menu pick to export the snippet! And, a bit of Googling failed to turn up any results (as in 0 results, odd). Does anyone know how to enable the menu pick?
Also, I went into Tools / Options, checked off "Show all settings" - and I was unable to find any relevant option that may enable snippet management.
When I go to the Snippet Manager, apparently it is expecting to already have a Snippet XML file to add, and won't give me some dialog to build my own new snippet.
Thanks for your answers.
Apparently, although it dances around the subject, it mentions that you must have Snippet Designer, but no info on how to install it or where to get it! You can obtain it from the GitHub repository at https://github.com/mmanela/snippetdesigner

VS 2013 opens the diff window when a code review item is marked as done

My team uses TFS 2013/Visual Studio 2013 to do code reviews. It all works fine but there is a really annoying thing which VS does that I can't seem to turn off.
If I submit a review and it comes back with suggested changes, I go through and make them, checking each one off as I go. The problem is each time I mark a code review item as done by checking the box to the far right of it in the Team Explorer -> Code Review view, VS opens the diff window for that particular item showing the review comments. I don't want to see any of that, I just want to mark the item as done so I know I've dealt with it.
Is there any way to prevent VS from showing the diff window when you mark a code review item as done?

How to quickly switch between designer and source code mode in QtCreator?

Is there a functionality like View Code in Microsoft Visual Studio where we can instantly go to the source code relating to the control/or form we are coding?
At the moment there is only an Edit button on the left upper corner of QtCreator which when clicked shows some xml related codes (design related I guess).
I have to double click on the source code I need to work on. Is there a way or plugin to directly navigate to the active source code?
I believe what you are looking for is Shift+F4

Collection was modified; enumeration operation may not execute

VB.NET 2010 project, VS 2010, VSS (think it is 2008).
looking at other posts for this error, seems it is because of a change in a loop, enumeration, etc... In my case, all I do is open the project, make any change, like re-sizing the form, save and close and when I reopen that form I get this error. then I can undo checkout of the code and it opens fine. Not even making a change to any code, just re-size the form. ANY change I make, gets this error. The code is in production already and works fine, and I think it only happens on my pc.
Help! Thank you in advance...
adding - actually it looks like it only happens in changes in the form, and the error is only on the form, not the code. But it happens on any form.
A coworker figured it out for me. It was an issue with DevExpress windows controls and Visual Studio.
Solution is here:
How to enable visual inheritance for Developer Express controls.

Resources