Visual Studio Feedback System on, 10:51 PM: We’ll keep you posted on any updates to this feedback. In case you need answers to common questions or need assisted support, be sure to use. Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. Visual Studio Feedback System on, 04:53 PM: I have also experienced the same problem with all of my local databases and any table. The team will review the feedback and notify you about the next steps. We have directed your feedback to the appropriate engineering team for further evaluation. Thanks a lot for providing the information. (private comment, text removed) Fiona Niu on, 07:33 AM: From instance 1 of VS, I created a new VS instance and started a recording. Note: Running as local admin without any solution/project open. Trying to capture a recording of the VS 2019 Enterprise 16.1.4 crash from SQL Server Object Explorer, following the instruction of support by creating a new instance of VS prior to clicking on Record. The VS Feedback tool has an issue: 1) the screen preview inaccurately shows a blank VS main window when I'm seeing a table of results and the "Filter and Sort " dialogue box from the SQL Server Object Explorer window, 2) I think the feedback recording is not submitted properly if the instance of Visual Studio associated with the Feedback tool crashes and relaunches during the recording. Must be non-negative and less than the size of the collection. I am getting an error when sorting even a local table by any column in the SQL Server Object Explorer "View Data" window without getting a pop-up window titled "Microsoft Visual Studio" with a white x on a red circle stating "Index was out of range. We look forward to hearing from you! Cory Langston on, 07:12 PM: For information about what data is collected, see
#VISUAL STUDIO SERVER EXPLORER TABLE FULL#
For security reasons, your files come directly to us and don’t appear on Developer Community.įor the full instructions, please see. You will be able to see the comment on Developer Community. Wait a few minutes for Visual Studio to collect and package the information that you recorded. When you’re done, choose the Stop Record button. When the Steps Recorder tool appears, perform the steps that reproduce the problem. Since this issue is now marked as Need More Info, that workflow is enabled in the Feedback Tool:Ĭlick the banner letting you know that you have problems requesting your attention.Ĭlick “View their request and respond” from the problem details bannerĪdd a comment, in the Attachments/Record: click Start Recording This will ensure that we collect the needed information for you without worrying about what to provide (recording, dump file or ETL trace). The easiest way to provide all the information is to use the Visual Studio Feedback Tool. Unfortunately those aren’t enough and more information is needed in order to investigate it further. I’ve tried to reproduce and investigate using the description, and attachments already provided. Thank you for taking the time to log this issue! Original Comments Fiona Niu on, 02:52 PM: On a datetime column, click sort by Ascending/Descending.Browse any local/remote SQL database for a table to view.Sorting a table in SQL Server Object Explorer causes Visual Studio to prompt with an index error popup and crash. Visual Studio 2019 16.1.4 crashes when sorting a table in SQL Server Object Explorer by datetime column
#VISUAL STUDIO SERVER EXPLORER TABLE PLUS#
I know some purists would quiver at the thought of treating a database table like a spreadsheet, but semantically they are not a world apart, plus this is supported in SSMS.This issue has been moved from a ticket on Developer Community. Does anybody know of a plugin I can use with VS 2012 to bring back this functionality? It seems odd to me that Microsoft have two different development trajectories with SSDT and SSMS? Are they designed to serve different purposes? Can SSMS be integrated into the Visual Studio IDE? I'd rather have a unified development environment if possible.Īny thoughts on a workaround for this problem would be much appreciated. This means I now need to go into SSMS to make these kind of quick updates. It seems to have only affected SQL 2012 instances, but from the Server Explorer I can no longer right click on a table "Show Table Data", pop open the SQL pane, query the data then perform inline edits on the results (as if I were modifying a spreadsheet). I'm pretty sure Microsoft have pulled one of the most useful features for performing quick edits on a SQL Server Database within the Visual Studio IDE.
0 kommentar(er)
