Visual studio 2019 ui нет
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I am new to Visual Studio. I want to create first Windows Application with UI. But, there is no option for UI under Projects/ Add new Item/.
Please guide , how to add UI.
All replies
In order to create an application that offers UI, choose an appropriate project type in “Create a new project” dialog. Some of the popular types:
If you do not see these projects, then probably your Visual Studio is incomplete. You will have to install the missing components using Visual Studio Installer.
For example, you can start with Windows Form App. Then you will see the main form, where you can place your UI controls: buttons, textboxes, etc., which can be found in Toolbox. You can also add more forms.
Give some details about your type of project.
Did you create a Windows Form App?
If so, the UI controls are in the ToolBox in the menu View-->ToolBox and then drag the control you want into the form.
If you do not create a winform project, please check the installer and make sure all the tools in the Workloads desktop development are installed successfully.
If l misunderstand your issue, please provide more information about your project type and some screenshots.
Any feedback will be expected.
- Proposed as answer by Lance Li-MSFT Microsoft contingent staff Wednesday, August 28, 2019 6:04 AM
Any update for this issue? Sorry to disturb and just want to confirm if this issue is solved or not.
And please check if Viorel's or Perry's reply helps to resolve your issue, if so, you can consider marking it as answer to indicate this issue is resolved, which benefit other members with similar issue.
As for the issue you get:
And if you can't find the UI designer window, for winform project please double-click the Form1.cs file. For wpf and UWP project, you can double-click the xx.xaml file to open the designer.
After that, you don't need to add UI by Projects/Add new item, you can find the UI controls you need in Toolbox like what Perry suggested, and just drag the control to your designer window.
Look forward to your reply. Have a nice day!
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
Everything is in the title,
I've installed VS 2019 (community) and it fails to open the designer for some Forms (winform).
This is the error it shows :
I've made some investigations and it seems that all files of the project are open as "miscallaneous files".
The same project opened in VS 2017 is working fine.
This is what I get from "Project System Tools" plugin, when opening the designer for one form :
Can you help me ?
I could not manage to create a sample to reproduce the issue. the projects that fails have numerous referenced projects.
Also, I forgot to mention that I already tried several operations : clean .vs/bin/obj folders, rebuild everything, remove/re-add the files.
All replies
Sorry for delay in reply.
Did you install some extensions for your project? If not, please unload the project in solution explorer, then reload your project.
Note: right click the project / unload Project/ reload Project
If the issue persists, please edit XXX.csproj file when unload project, check whether the section is form.
Note: right click the project / unload Project/ edit XXX.csproj file
Any feedback will be expected.
Thank you for taking time to find a solution for the issue.
Answers to your questions :
- Did you install some extensions for your project ?
Nope - Unload/Reload the project ?
Already tried that, still not working - The form that cannot be designed, in the vbproj :
- It works (the form can be designed) on VS 2017 community but not in VS 2019 community
- I have the last version of VS 2017 community and 2019 community
- This is not workstation-dependent - I have the same issue on all computers I could test on
Thank you for reply.
According to your description, it seems that it is not compatible with VS2019. Did you have some third extensions or plugins which could not be used in the VS2019? Or did the project need specified options and environment? Please run the VS as safe mode to open your project.
Note: open RUN window / type "devenv /safemode"
To your first question, about any plugin not compatible with VS 2019, I don't know yet. I'm checking.
Running VS2019 in safemode bring multiple issue during the project loading "The visual studio build manager package package did not load correctly. The problem may be caused by a configuration change or by the installation of another extension. You can get more information . activitylog.xml"
And this is the activityLog.xml which seems to log somee exceptions during the loading process: ufile.io / jstv1ode
This is an entry in this file :
It seems to be the root cause of the issue ?
Edit: Actually there are quite a lot of exceptions thrown in activitylog.xml, I don't know which one is relevant.
NB: Also, in safemode, I cannot build. It says there is an error, but no error is shown.
Thank you for feedback.
Based on your description, It seems that there are some extensions which could not run in the visual studio 2019. Please have a try to uninstall them, then check if the winform could be recognized by VS IDE.
Look forward to your reply.
Sorry for delay in reply.
I was looking forward any extension in our solutions that could not be loaded in VS 2019.
Unfortunately, there are no extensions incompatible with VS 2019.
BUT I managed to reproduce the issue with a simple project. You can get the project here : we.tl / t-8KqKKAtNUK
(remove spaces to get a valid link)
I took the project that fails, remove all the files, and just add a single form.
Build it and try to open Form1 in the designer with VS 2019, it should not works.
If you try to open it with VS 2017, it will works.
Let me know if you have the same issue as me and if you have any idea what is wrong with the project itself.
I found the issue.
If you define constants (Project > Compile > Advanced Compile Options . > Custom constants), which concatenated, have more than 190 characters, then the project is not correctly loaded, and thus project files are interpreted as Miscallaneous.
You can easily reproduce the regression yourself. Create a Winform (VB) project, and add the following Constant :
NB: This constant has a length of 191 characters.
NB2: You are allowed to add this constant via UI. There is no error shown when entering the constant.
Open the existing form in the designer, and you'll see that the designer cannot load the form.
Now, remove only one character from the previous constant, save, reload and you'll see that the designer can finaly load the form.
Now, what should I do ? Is there any bug tracking platform, or something like that to share the regression ?
Because it works on VS 2017.
I tried to alternate from Solution Explorer as well from menu View → designer option, but it is still not showing a form. What is going wrong there?
I made a Google search for this, but I did not find anything useful on this.
Please check in the image that I'm getting during the opening project.:
Push Shift+F7 , which is the shortcut to open the designer. You should also be able to access it using the Solution Explorer on the right-hand side of your VS environment.
2 Answers 2
Make sure you only have the form declared in your file. If you have more than one class defined, the design viewer will not work.
This helped me, the designer worked fine until I added another class to the same file. It worked again when I removed the new class.
This was my issue. I had another class in the same file as Form1.cs. When I removed the class, the designer worked again.
Omg, what a nightmare that was. I created an EventArgs class in the same file as the control. VS should issue a warning or something about that. You saved me a LOT of time, no way I would have realized that on my own.
Preview Visual Studio 2019 until v16.4 needs a VSIX separate installation extension. Now you can update your Preview of Visual Studio 2019 (to 16.5 or higher) and you don't need this extension. You can do it through the menu "Help" of the Visual Studio IDE.
After the update, go to menu Tools → Options → Environment → Preview Features and check the "Use previews of the .NET Core SDK (requires restart)" option.
Restart Visual Studio and it will work ;)
You can install the Preview Version that will have all these and more feature enabled. As it’s a preview, it may be unstable, but it can run side by side with your normal version in case something is broken in preview.
Мы рады поделиться с вами сегодня тем, что в рамках разработки Visual Studio 2019 мы обновим нашу тему, обновим значок продукта и заставку. Эти изменения в рамках UX/UI дизайна поможет быстрее приступать к работе. Мы бы очень хотели, чтобы вы высказали свое мнение об этих обновлениях. Каждый комментарий влияет на будущий продукт.
В качестве КДПВ у нас сегодня первое изменение: Значок Visual Studio 2017 (слева) и новый значок Visual Studio 2019 (справа)
Эта статья — перевод статьи из нашего Vusial Studio Blog.
Итак, первое изменение: мы решили обновить значок в VS2019. Отчасти это делается для того, чтобы пользователю было проще различать, какую версию программы он открыл и использует. Мы столкнулись с некоторыми проблемами юзабилити стиля значка на ранних этапах выпуска Visual Studio 2017, и мы сосредоточены на решении этих проблем в Visual Studio 2019.
Одна из проблем, которая возникла, заключалась в том, что плоский стиль текущей иконки сделал ее почти невидимой на фоне аналогичного цвета. Переняв Fluent Design System и применив его к глубине, освещению и материалу, мы визуально улучшили значок, чтобы он был намного более заметным на разных фонах.
Еще одна проблема, с которой мы столкнулись, — это разница между превью и окончательной версией Visual Studio. С помощью значков можно решить эту проблему, но в VS2017 появились другие сложности. Для Visual Studio 2017 значок был разработан как часть большой семьи продуктов Visual Studio. Метод, который мы использовали, состоял в том, чтобы у каждого значка была «ленточка» с правой стороны. Однако это оставило меньше места для самого логотипа.
В Visual Studio 2019 мы удалили все дополнительные части значка. Мы хотим сосредоточиться на самом узнаваемом элементе логотипа Visual Studio: а именно, на бесконечной петле.
Мы увеличили размер бесконечной петли, что дало нам больше возможностей показать разницу между значками Preview и Release. Мы использовали более смелый подход к Preview-logo. Разделив форму значка в нескольких местах, мы сохранили общую форму значка Visual Studio. Но мы показываем четкую разницу между Preview и Release.
Мы работаем над аналогичным подходом к новой иконке Visual Studio для Mac, которая дебютирует в предстоящих анонсах.
Легче запускать код
Стартовое окно в Visual Studio for Mac (слева) и Visual Studio (справа)
Благодаря исследованиям и наблюдениям мы определили пути упрощения выбора, который вы должны сделать в ходе наиболее важных шагов в начале работы с Visual Studio. Мы поняли, что нам нужно удалить то, что мы называем «трамплинами наружу», и предоставить вам наилучшие пути к коду.
Независимо от того, являетесь вы новичком или опытным разработчиком Visual Studio, новое окно запуска предоставляет быстрый доступ к наиболее распространенным способам начала работы разработчиков с кодом: клонирование или проверка кода, открытие проекта, открытие локальной папки на ПК или создание нового проекта.
Наконец, мы также переосмыслили опыт создания нового проекта с новым списком самых популярных шаблонов и улучшенными возможностями поиска и фильтрации. С новым дизайном и пошаговым подходом выбора шаблона и его настройки, мы считаем, что сделали его менее перегруженным, чтобы вы могли сосредоточиться на одном решении за раз. Вы также сможете изучать другие языки, платформы и типы проектов, поддерживаемые Visual Studio, и в конечном итоге сможете установить их без проблем.
Обновленная голубая тема
Обновленная голубая тема (слева) рядом с текущей синей темой (справа)
Одним из наиболее заметных визуальных эффектов, которые вы можете увидеть при запуске Visual Studio 2019, является наша обновленная голубая тема. Более половины из вас используют синюю тему, но она не менялась в VS2012. Мы сосредоточились на желании обновить интерфейс Visual Studio. Мы внесли небольшие изменения в весь пользовательский интерфейс, сгладили углы.
Производительность у вас под рукой
Текущее пространство (вверху) и упрощенная версия для Visual Studio 2019 (внизу)
В поисках возможностей для уменьшения беспорядка, мы начали с панели инструментов. Удалив строку названия файла, мы смогли переосмыслить панель инструментов Visual Studio без существенного изменения рабочего процесса. Мы изменили поиск: в предстоящих версиях вы увидите, что поиск в Visual Studio 2019 более мощный и точный.
Live Share теперь имеет стабильное место в интерфейсе. Там же видно людей, с которыми вы работаете.
Заметные уведомления
В начале следующего года в одном из наших предварительных выпусков будет обновлен пользовательский интерфейс уведомлений. Из исследований: текущие уведомления не до конца устраивают разработчиков. Теперь уведомления будут появляться в строке состояния в нижней части IDE. Это поможет разработчикам не терять концентрацию во время работы.
Visual Studio 2019 pushes the boundaries of individual and team productivity. We hope that you will find these new capabilities compelling and start your upgrade to Visual Studio 2019 soon.
As you are considering this upgrade, rest assured that Visual Studio 2019 makes it distinctively easy to move your codebase from previous versions of Visual Studio. This post captures the reasons why your upgrade to Visual Studio 2019 will be pain-free.
- You can install the latest IDE side-by-side with any older VS versions
- You can continue building your C++ code with the MSVC v140 (VS 2015.3) or v141 (VS 2017) toolsets
- You can upgrade to the latest MSVC v142 (VS 2019) and maintain binary compatibility with any of your 3rd party libraries that haven’t migrated yet
- Regardless of the toolset you’re on, you get access to the full collection of OSS libraries available in Vcpkg
Side-by-side Visual Studio Installations
You can install the latest version of Visual Studio on a computer that already has an earlier version installed and continue to use both versions in parallel with no interference. This is a great way to try Visual Studio 2019 or adopt it for some of your projects. The Visual Studio Installer will let you manage installations of Visual Studio 2017 and 2019 from a central UI.
MSVC v140 (VS 2015.3) and MSVC v141 (VS 2017) Toolsets in the Visual Studio 2019 IDE
Even if you are not ready yet to move your project to the latest toolset (MSVC v142), you can still load your project in the Visual Studio 2019 IDE and continue to use your current older toolset.
Loading your existing C++ projects into the IDE will not upgrade/change your project files. This way, your projects also load in the previous version of the IDE in case you need to go back or you have teammates that have not yet upgraded to VS 2019 (this functionality is also known as project round-tripping).
Toolsets from older VS installations on your box are visible as platform toolsets in the latest IDE. And if you are starting fresh with only VS 2019 installed on your machine, it is very easy to acquire these older toolsets directly from the Visual Studio Installer by customizing the C++ Desktop workload (with the Individual Components tab listing all the options).
New v142 toolset now available
Within the Visual Studio 2019 wave (previews, its general availability, and future updates), we plan to continue evolving our C++ compilers and libraries with
- new C++20 features,
- faster build throughput, and
- even better codegen optimizations.
The MSVC v142 toolset is now available and it already brings several incentives for you to migrate.
VC Runtime in the latest MSVC v142 toolset is binary compatible with v140 and v141
We heard it loud and clear that a major reason contributing to MSVC v141’s fast adoption today is its binary compatibility with MSVC v140. This allowed you to migrate your own code to the v141 toolset at your own pace, without having to wait for any of your 3rd party library dependencies to migrate first.
We want to keep the momentum going and make sure that you have a similarly successful adoption experience with MSVC v142 too. This is why we’re announcing today that our team is committed to provide binary compatibility for MSVC v142 with both MSVC v141 and v140.
This means that if you compile all your code with the v142 toolset but still have one or more libraries that are built with the v140 or v141 toolset, linking all of it together (with the latest linker) will work as expected. To make this possible, VC Runtime does not change its major version in VS 2019 and remains backward compatible with previous VC Runtime versions.
When you mix binaries built with different supported versions of the MSVC toolset, there is a version requirement for the VCRedist that you redistribute with your app. Specifically, the VCRedist can’t be older than any of the toolset versions used to build your app.
Hundreds of C++ libraries on Vcpkg are available regardless of the toolset you’re using
If you are using Vcpkg today with VS 2015 or VS 2017 for one or more of your open-source dependencies, you will be happy to learn that these libraries (close to 900 at the time of this writing) can now be compiled with the MSVC v142 toolset and are available for consumption in Visual Studio 2019 projects.
If you are just getting started with Vcpkg, no worries – Vcpkg is an open-source project from Microsoft to help simplify the acquisition and building of open-source C++ libraries on Windows, Linux, and Mac.
Because v142 is binary compatible with v141 and v140, all the packages you’ve already installed will also continue to work in VS 2019 without recompilation; however, we do recommend recompiling when you can so that you can enjoy the new compiler optimizations we’ve added to v142!
If you have VS 2019 Preview installed side-by-side with an older version of VS (e.g. VS 2017), Vcpkg will prefer the stable release, so you will need to set Vcpkg’s triplet variable VCPKG_PLATFORM_TOOLSET to v142 to use the latest MSVC toolset.
MSVC compiler version changes to 19.2x (from 19.1x in MSVC v141)
Last but not least, the compiler part of the MSVC v142 toolset changes its version to 19.20 – only a minor version increment compared with MSVC v141.
Note that feature-test macros are supported in the MSVC compiler and STL starting with MSVC v141 and they should be the preferred option to enable your code to support multiple MSVC versions.
Call to action
Читайте также: