WPF vs WinForms performance

Performance comparison of Winforms and WPF - Stack Overflo

Overall WPF desktop applications performs significantly better than equivalent WinForms code, in scenarios that require a sophisticated UI, styles customization, and graphics-intensive scenarios, due to several architectural advantages of WPF over WinForms Compared to what WPF has currently, WinForms has more online resources, third party controls and developer communities. Moreover, you can easily find a WinForms developer vs-WPF developer for your project. Compared to WPF, WinForms has much better design-time experience in Visual Studio. This itself is enough to choose WinForms I was wondering if any one could point me to some information that provides a basic performance comparison of windows forms vs WPF. I need to be able to explain/demonstrate that WPF performance is on par with win forms. I've been googling and looking around on blogs but have yet to find a decent comparison with any type of actual data that compares the performance. Most articles/posts seem to just compare the concepts that might sway your decision either way Wenn es schnell gehen soll, dann setzt man eher auf Winforms. Windows Presentation Foundation und Windows Forms versus Web Entwicklung. Online Applikationen werden immer häufiger genutzt. Sei es von Unternehmen oder von Konsumenten. Dadurch werden immer weniger Applikationen auf Basis von WPF oder Winforms entwickelt. Viele steigen gleich bei ASP.NET, dem Web Application Framework von Mircosoft ein, um damit Web basierte Applikationen zu schreiben und den Nutzern bereitzustellen Winforms is a legacy framework to build desktop applications while WPF is the main framework promoted by Microsoft to build desktop applications. In this article we will uncover the differences between WPF vs Winforms

WPF and Windows Forms: These .NET-based platforms provide a common type system, APIs, and application model for managed applications. Win32: This is the original platform for native C/C++ Windows applications that require direct access to Windows and hardware. This makes the Win32 API the platform of choice for applications that need the highest level of performance and direct access to system hardware Microsoft's official 2019 WPF roadmap states that functional and performance parity compared to the .NET Framework are set goals in regards to the release of .NET Core 3.0. The roadmap also states that there needs work to be done in order to have all components available and that they are working on the process of how to validate and merge community pull requests WPF platform is newer than WinForms and still evolving. At the end of 2014, Microsoft announced WPF roadmap, which focused on quality and performance. And the latest.NET Framework updates prove that they keep moving in this direction:.NET 4.6.1,.NET 4.6.2. UWP is another XAML platform that's being actively developed Windows forms have less learning curve. Whereas WPF has more learning curve as required to understand the full flow of controls and design part. Windows forms are less time consuming or less tricky. WPF is trickier and more time to consume for getting the things in place while developing the applications As you can see, CPU usage with WPF while scrolling was horrible. And the experience too. UWP scroll is way smoother than WPF. You'll notice it better when you use touch. A few points

The main issue is that the time you save on figuring out scaling is more than consumed by the time you spend on design. WPF is a designer-centric framework. It will repay your efforts, but if you just want to slap a couple of grids and a few buttons on a form to get a working business application, Windows Forms remains tempting WPF vs WinForms -Control by control ListBox - WPF is the clear winner. This was turned from an unexciting to a really great control. ComboBox - Again WPF is the clear Winner. TreeView - I like the WPF treeview better as it is much more flexible but the WinForms one is significantly easier to use. I would call this one a tossup. RichTextbox - The WPF Richtextbox is glacially slow in. WinForm vs WPF vs UWP vs Console - The C# Desktop UI Showdown (and the future with .NET 5) - YouTube. Today Deserves Delivery - Full Spot. Watch later. Share. Copy link. Info. Shopping. Tap to. It is unfortunate that I would have to host a Winforms control on my WPF project to ensure decent performance, but it certainly is a workaround that works. Just to let everyone else know, you'll need to add references to System.Windows.Forms, and WindowsFormsIntegration to your WPF project for the above answer to work

WPF vs WinForms: 19 Pros + Cons To Uncover The Difference

Optimizing Performance: Taking Advantage of Hardware. 03/30/2017; 3 minutes to read; a; In this article. The internal architecture of WPF has two rendering pipelines, hardware and software. This topic provides information about these rendering pipelines to help you make decisions about performance optimizations of your applications. Hardware Rendering Pipeline. One of the most important. WinForms/WPF: Windows Forms, that's probably about 17 years old now going strong, very, very productive. WPF, probably about 15, and again, super-rich XAML, C#-based code base that you have, an ecosystem and the tooling. Both of those things are so strong and they don't need to be like the old school, 10-year-olds WPF or WinForm sub. They could look more than fresh and they run on .NET. Performance comparisons show that: LightningChart .NET large data set rendering performance is approx. 37,200 % better than the average of others. LightningChart .NET real-time rendering capacity is approx. 2,300,000 % better than the average of others

Simon de Uvarow - Grado 1 - Universidad de la República

For more such videos visit http://www.questpond.comFor more such videos subscribe https://www.youtube.com/questpondvideos?sub_confirmation=1See our other Ste.. Generally speaking, both are worth knowing. WPF and UWP are both constrained by the classic Windows API. WPF uses Windows windows with a window handle and all that. UWP can be frustrating (async/await at least) due to it's dependence on classic Windows. It is my understanding that many companies still use Windows Forms C# Compare Windows Forms vs WPF vs UWP What kinds of desktop applications can you make in C# with Visual Studio? Which kind is recommended

The options where WinForms vs WPF, and it looked like WPF is the new but already widely used and promising framework with bright future while WinForms is something old which will be abandoned by everyone in favor of WPF. And we selected the WPF without thinking a lot - because you do not select an old deprecated technology if there is a new technology on the market which comes to replace the. So, WinForms, WPF or the New Modern Desktop App (WinUI UWP) ? Let's first say some words about WinForms versus the other options This is the framework for Windows desktop applications that was introduced at the same time as .NET itself, back in 2002 There are many way that you can measure the performance between them, but winform will perform better due to many reason. But if you measure the UI features WPF datagrid provided, winform will never beat that. So there is a trade off between performance and UI features but if you decide to use WPF then you could follow below point to improve performance. There is a WPF performance suite.

WPF / Winforms Performance Compariso

WPF vs WinForms : Ch Syam Kumar. Thursday, April 16th, 2020 Web. When it comes to building a desktop application for Windows PC, you have to choose from Universal Windows Platform (UWP), Windows Presentation Foundation(WPF) , Windows Forms (WinForms) and Win32. Both WPF and Windows Forms feature a common type system, APIs and application model for managed applications running on .NET. Hallo .NET Freaks, eine Frage die mich interessiert, und die sicher von allgemeinem Interesse ist: Wer hat Erfahrung mit umfangreicheren WPF Projekten in VS 2008, wo es um normale Business Applikationen geht, die vielleicht von WinForms nach WPF migriert wurden. Kann man in etwa sagen ob die grafische Performance der Benutzeroberfläche besser oder schlechter als bei WinForms Anwendungen ist WPF vs WinForm with What is WPF, ListBox, Features, Controls, Treeview, Canvas, border, groupbox, timer, WPF viewbox, richtextbox, WPF ImageSource, WPF XAML etc Our number one priority is to enhance startup performance for WPF apps with complex Office-inspired user experiences. We expect to optimize startup performance for the following UI controls in 2021: Spreadsheet; Rich Text Editor; Ribbon layouts with multiple pages / merging operations. Once complete, we expect to substantially improve startup performance: Theme Preload Enhancements. We expect.

GitHub - ServiceStackApps/ReactDesktopApps: Docs for

Winforms versus WPF: Ein Vergleich - Yuhir

  1. Thus although WPF windows and WinForms forms look similar, what happens behind the scenes is completely different. Following that brief introduction, let's start looking at 10 reasons why WPF is a better bet for developing systems. 10 reasons why WPF is better than Windows Forms (this blog) WPF Forms are Quicker to Create.
  2. The WinForms and WPF controls are available today as a preview in the 3.0 release of the Windows Community Toolkit in the Microsoft.Toolkit.Win32.UI.Controls package. This means that upgrading from the Trident-powered WebBrowser control to the EdgeHTML-powered WebView in your WinForms or WPF app can be as easy as dragging in a new control from the toolbox
  3. utes to read; a; In this article. This section is intended as a reference for Windows Presentation Foundation (WPF) application developers who are looking for ways to improve the performance of their applications. If you are a developer who is new to the Microsoft .NET Framework and WPF, you should first familiarize yourself with both.
  4. I think it's still at the point where both are excellent, valid choices. Right now, all Microsoft's energy is in UWP. UWP is excellent, but for me has two main drawbacks: 1. It's Windows 10 only, anything you write in UWP will only run on Windows.
  5. Some time ago I wrote a post about converting a WPF application into .NET Core. One thing that called my attention in this Build 2019 talk was that the performance for file enumerations was enhanced in the .NET core apps. So I decided to check this with my own app and see what happens in my machine. I added some measuring data in the app, so I could see what happens there
  6. UWP, WPF, and WinForms have amazing Control suites from companies like Telerik; In Electron you can take advantage of the huge amount of web libraries and controls available ; While C++ is not the most productive language when compared to C# or Java, it makes sense to use Qt when your application is heavily interacting with a C++ native layer. Note that It's also possible to use .NET with a.

WPF vs Winforms. Which should you choose ? - Chubby Develope

Choose your Windows app platform - Windows applications

  1. The trouble is that GDI painting isn't great for performance and you have to play games with double buffering to prevent flickering. WPF uses retained graphics, which is somewhat easier on you. You can create all your shapes and images, give them to WPF and update them when need be. WPF will automatically redraw what needs redrawn and properly sort everything for you. It also has the benefit.
  2. There is no shortage of information out there on how to speed up the performance of WPF applications, but too often the focus is on the weird stuff instead of the simpler issues. I'm not going to talk about things like writing to WritableBitmaps to optimize drawing—it's a topic covered to death elsewhere. Instead, this is meant to be a slightly more practical guide to squeezing.
  3. The WinForms and WPF controls are available today as a preview in the 3.0 release of the Windows Community Toolkit in the Microsoft.Toolkit.Win32.UI.Controls package. This means that upgrading from the Trident-powered WebBrowser control to the EdgeHTML-powered WebView in your WinForms or WPF app can be as easy as dragging in a new control from the toolbox
  4. utes to read; a; In this article. Windows Presentation Foundation (WPF) data binding provides a simple and consistent way for applications to present and interact with data. Elements can be bound to data from a variety of data sources in the form of CLR objects and XML. This topic provides data binding performance recommendations. How.
  5. Search for jobs related to Winform vs wpf performance or hire on the world's largest freelancing marketplace with 19m+ jobs. It's free to sign up and bid on jobs
  6. WPF is a more modern take at UI design that provides many benefits over WinForms, including performance (WinForms uses GDI+, which does not use graphic acceleration, while WPF is built on top of DirectX), more flexibility in UI design, and cleaner separation between code and UI. WPF uses XAML, a technology shared with WinRT and Silverlight - so if you are planning to also develop modern.

The overall performance of the charting solutions available to WPF (and Silverlight) developers is improving. However, the performance of the WPF rendering system appears to create an upper limit which constrains what can be achieved. The raster-based approach is not subject to these same constraints and as a result provides a considerable improvement in performance I've been often asked how to improve performance of WinForms apps so here is the list of my top suggestions and further reading recommendations on how to speed up your Windows Forms applications: Reduce modules loaded by your application to increase start-up time. Remove all references from your project that are not used. Click here to read MSDN article on that on other techniques. Pre. WPF was released back in 2006 as a successor to WinForms. It introduced the XAML language for declaratively defining the UIs. It also introduced the use of Direct3D for rendering. This allows.

Is WPF Still Relevant in 2019? Claudio Bernascon

  1. A question about WinForms versus WPF regarding GUI performance https://softwareengineering.stackexchange.com/questions/418956/a-question-about-winforms-versu..
  2. The final topic in our .NET 5 Breaking Changes series is WPF and Windows Forms. These desktop technologies were unavailable before .NET Core 3.0, as earlier versions of .NET Core focused on web-base
  3. Winforms vs WPF both are mainly used for the same purpose for developing and designing windows applications, but WPF can be used for the web application. The difference between them is scalability, performance as WPF can render fast compared to windows forms, complexity, and support
  4. I see Josh Smiths has posted his view on WPF vs Windows Forms. Here's my current view (although I reserve the right to change it at a later date :) ) Windows Forms is legacy. Microsoft should label Windows Forms as legacy (as it has done with COM), only offer bug fixes and concentrate 100% on WPF.

Winforms is referred to as Windows Forms. It is a graphical user interface for.Net framework desktop applications. It has a set of managed libraries in .net framework. It offers an extensive client library to provide the interface to access the native windows graphical interface elements and graphics from managed code. WPF is abbreviated as a Windows presentation framework when it comes to WPF vs forms, it's like comparing a tricycle to an airplane, sure the airplane is much more difficult to operate, the tricycle is easy, but you can only go so fast and so far, I find it funny how all the non-WPF know so much about it, kinda like the 4 year old aviation expert , I can get anywhere I want or need to go on my three wheels, slow and steady I Say! Loading. Compared to what WinForms had at that time, it was true that the WinForms visual designer offered much better performance and reliability. Since then, the Visual Studio team improved the WPF. You can embed WPF controls in a WinForms application or WinForms controls in a WPF application, using a simple adapter. Because of this inherent symmetry, you can build hybrid applications, mixing controls from the other platform. Michael Sorens gives a practical guide to WPF / WinForms interoperabilit

Ist WPF, ohne den höheren Performance-Anspruch zu berücksichtigen, immer GDI+ vorzuziehen? Ich würde WPF nicht mit GDI vergleichen, sondern eher mit WindowsForms. Also erstmal stellt WPF Controls zu Verfügung genauso wie Windows-Forms. Zitat: Ist WPF für 2D-Spiele geeignet? Wenn man mit Windows.Forms 2D Spiele machen kann, wir das auch mit WPF gehen. Zitat: Kann mir jemand gute Tutorial. WPF vs. WinForms. Jason Jefferson December 14, 2017 0 Comments In the previous chapter, we talked about what WPF is and a little bit about WinForms. In this chapter, I will try to compare the two, because while they do serve the same purpose, there is a LOT of differences between them. If you have never worked with WinForms before, and especially if WPF is your very first GUI framework, you. WPF vs. Windows Form. One benefit big corporations provide to their IT people is that they don't have to keep up with the latest technology to keep their job. That's why it is 4 years after WPF was introduced with Visual Studio 2005, I learned about it for the first time. WPF (Windows Presentation Foundation), a component of Microsoft .NET Framework 3.5, is a new platform for building rich. Hello, I'm building an OLAP client that downloads lots of data. The data is added programmatically to DataGridView row by row. Which is faster? Windows form DataGridView or WPF DataGrid? Thank you · Hi, There are many way that you can measure the performance between them, but winform will perform better due to many reason. But if you measure.

DotNet Developer Blog: Difference between Static variable

Comparing .NET Core 3.0 Winforms and WPF APIs vs. NET Framework 4.x with NDepend. Core Runtime and API improvements and also more performances. it would be just as easier to port our WPF/FF code to another stack other that core , maybe that explains whhy almost no one is adopting core, just have a look a the pathetic Nuget downloads and the Wc3tech marketshare numbers, it's not a no. FlexGrid scrolling performance (WPF vs WinForm) Originally Posted 24 November 2014, 1:36 am EST. Please to follow topic. utys01. Post Options: Link. Copy. Originally Posted 24 November 2014, 1:36 am EST. Hi, currently we are evaluating if we should use WPF or WinForms for a new business application. The main focus of this app will be data-representations of database tables in grids. Today we'll see something that I was so excited to see how it works: .NET CORE for WPF, it's not completed yet but we can do some things! Today I'll create a.. Winforms et WPF sont utilisés pour développer et concevoir les applications Windows, mais WPF peut également être utilisé pour les applications Web. La différence entre eux réside principalement dans l'évolutivité et les performances, car WPF peut afficher un rendu rapide par rapport aux windows forms. WPF est principalement utilisé car il s'agit du dernier-né et offre de bonnes. WinForm vs WPF vs UWP vs Console - The C# Desktop UI Showdown (and the future with .NET 5) - Duration: 59:03. IAmTimCorey 88,231 views. 59:03 Microsoft released VS 2017 and Microsoft.NETCore.UniversalWindowsPlatform 5.3.0 with significant performance improvements on March 7, 2017. If you have performance problems with your UWP app, check it out with new versions. UWP and WPF platforms use.

FlexGrid Performance: Compare WinForms, WPF, UWP Performanc

Michael Sorens provides a handy wallchart to help migration between WinForm / WPF, VS 2008 / 2010, and .NET 3.5 / 4.0. this can be downloaded for free from the speech-bubble at the head of the article. He also describes the current weaknesses in WPF, and the most obvious differences between the two There's enhanced Machine Learning support with better support for ML.NET. ASP.NET Core is now an integral part of .NET Core as are WPF and WinForms, not separate installs. There's C# 8 support as well as .NET Standard 2.1 support. There's nascent support for WCF and .NET Remoting. Although it's not in Preview 1, there's planned support for Cosmos DB in EF Core 3 as well as better support for. wpf vs winforms performance. winforms vs wpf. wpf vs winforms 2017. c# cross thread invoke. winforms tutorial. wpf vs winforms vs uwp. 7 Jun 2013 12 Apr 2013 26 Apr 2012 The line of action is a simple curved line that evokes movement. Avoid making your line of action S-shaped or straight - it will hinder the overall WPF vs. WinForms. In the previous chapter, we talked about what WPF is and a. chossing between WinForms vs WPF * Which environment is better suited for delivering functionaly rich GUI in a RAD environment Thanks Amir. Bob Powell [MVP] 2007-12-11 18:49:05 UTC. Permalink. A company may wish to migrate an existing application to WPF to add a new look to the application, or, if the application was an intensely graphical one, to increase performance. Architecturally, WPF.


Top 11 WPF Performance Tips . Windows Presentation Foundation provides a very confortable way to develop rich user experiences. A drop shadow for example can added by inserting two simple lines of XML. But this simplicity can also mislead us to overuse them. This leads to performance issues. The following tipps may help you to avoid or fix them. Dispatch expensive calls either within the UI. However, with small amount of data, we haven't had any performance reports by other customers using the grid in a standard WinForms application in .NET environment. It seems that the problematic behavior was only in OpenEdge environment, because RadGridView relies on OE ProBingingSource component in order to load its data

Video: Winforms vs WPF Learn The Top 6 Most Awesome Difference

UWP vs WPF — A Simple ListView performance comparison by

DirectX 11 3D rendering engine for WPF and WinForms. Ab3d.DXEngine is a blazing fast 3D rendering engine that can be used in .Net Desktop applications. Ab3d.DXEngine uses super fast multi-threading rendering techniques that can fully utilize graphics cards and provide the ultimate performance that is almost the same as when using C++. The engine also supports top quality visuals with per-pixel. WPF vs. WinForms. In the previous chapter, we talked about what WPF is and a little bit about WinForms. In this chapter, I will try to compare the two, because while they do serve the same purpose, there is a LOT of differences between them. If you have never worked with WinForms before, and especially if WPF is your very first GUI framework, you may skip this chapter, but if you're interested.

A question about WinForms versus WPF regarding GUI performance. Ask Question Asked 5 months ago. Active 5 months ago. Viewed 63 times -1. I have some experience with WinForms and want to make a GUI for real-time plot of signals and also controlling hardware. I am planning to use WinForms for this and want to avoid WPF. My reasoning is that I don't need the outlook to be good looking but only. Uses hardware acceleration for drawing the GUI, for better performance; The ability to reuse existing code; Declarative vs. procedural code . CONS. Requires .NET Framework 3.0 ; Compared to Windows Forms, still in evolving phases. Requires Dx9 compatible video card for advanced graphics . When to use WPF & WinForms. It's clear that both the technologies have pros and cons to be considered. WPF checks the machine's hardware and software drivers that will be utilized to achieve optimal performance. Old computer/less powerful system? No problem! WPF can use the CPU instead. Moreover, WPF can downgrade the motion, transparency, etc., to run in older computers (check RenderCapability.Tier, for example). WPF uses XAML. XAML is built on top of the WPF API. XAML is an XML type of. Winforms vs WPF werden hauptsächlich für den gleichen Zweck zum Entwickeln und Entwerfen der Windows-Anwendungen verwendet, aber WPF kann auch für die Webanwendung verwendet werden. Der Unterschied besteht hauptsächlich in der Skalierbarkeit und der Leistung, die WPF im Vergleich zu Windows-Formularen, der Komplexität und der Unterstützung schnell wiedergeben kann. WPF wird.

Making the decision between WPF and WinForms however is a different story. Sure, WPF is the new hotness and WinForms is old and busted but is it the right choice? Obviously it depends on the situation and Microsoft is continuing to deliver and support WinForms so it won't be going away anytime soon. So what are the compelling factors to choose WPF over WinForms? Karl hints at choices of WPF. Windows Form Controls vs WPF Controls Part-2 (Performance Comparision) yash soman. Rate me: Please Sign up or sign in to vote. 4.60/5 (7 votes) 14 Oct 2015 CPOL 4 min read. The article is about window form controls and wpf controls performance. The difference between them and internals of how they are processed . Introduction. This is the analysis of the Windows form controls and WPF controls. I have read most of the major threads on WPF vs. WinForms and I find myself stuck in the unfortunate ambivalence you can fall into when deciding between the tried and true previous tech (Winforms), and it's successor (WPF). I am a veteran Delphi programmer of many years that is finally making the jump to C#. My fellow Delphi programmers out there will understand that I am excited to know that.

For me, I wouldn't use winforms unless I have to and if a team member doesn't understand the advanced concepts of wpf, they can just pretend it's winforms to get started and learn it along the way. Not trying to bag on winforms, just trying to see if there is something I'm missing since you can just treat WPF as a drag and drop environment like winforms (at least in the beginning). Continue. WPF is the latest one, so naturally the doubt arises whether the choice would be to go for Winforms or WPF. True, there are plenty of GUI interfaces that developers use to create webpages, but the most versatile ones are WPF and Winforms. Though both of these interfaces are so much alike, there are a lot of differences between the two WPF is better suited to this than WinForms; Will this be running on Windows XP? If yes, go with WinForms as you will be limited to an older WPF version that is missing a lot of the performance improvements introduced later on Permalink Posted 4-Jan-17 22:10pm. Pete O'Hanlon . Comments. Philippe Mori 5.

Bin ich doch vor Kurzem gefragt worden, mal die Nachteile von WPF aufzuzählen. Darüber hatte ich mir bis dahin noch keine Gedanken gemacht, da ich es noch nicht entscheiden musste. Hinterher fiel mir ein, bei WPF werden weniger Controls mitgeliefert. Das dürfte aber heute auch kein Problem mehr sein. (Codeplex usw.). Bezüglich Speicherverbrauch wurde ich heute mal neugierig: In Windows. While Microsoft and community developers have improved desktop dev tooling in .NET 5 and new open source implementations, the tech hasn't translated easily from the Windows-only .NET Framework, and catch-up efforts planned for next year's .NET 6 include high DPI support for one troublesome project, Windows Forms Is this worth it, vs. just moving and adjusting the existing screen setup and control event handler methods I have in the Winforms app? The core of my problem is that I am working with autogened code that takes advantage of the public string LotID { get; set;} syntax, that would need to be broken down into separate private fields and public properties for each field/property that is.

  • Barbie and the 12 dancing Princesses full movie.
  • Taubenschreck HORNBACH.
  • Zertifizierte Diamanten.
  • Language in Use EXERCISES C1 pdf.
  • Fassdauben Abdichten.
  • IE University fees.
  • Alkalifeldspat.
  • Panomax Zell am See.
  • Vögel in ihrem Lebensraum Arbeitsblatt.
  • Huk coburg kündigung auslandskrankenversicherung.
  • Abflug Lufthansa San Francisco.
  • Stevens Prestige 2021.
  • Santana Supernatural wiki.
  • Swisshaus Hemera.
  • C Pointer.
  • Partner optische Ähnlichkeit App.
  • Helikopter Eltern Anekdoten.
  • Majdan bosna i hercegovina.
  • Inlandsflüge Island.
  • Beinlängendifferenz Ursachen.
  • Body Condition Score Katze.
  • Rubbellose online.
  • Umweltamt Düren.
  • Circe JSON object.
  • F Kart alternative.
  • Santa Cruz Chameleon review.
  • Weight Watchers Punktetabelle PDF 2020 kostenlos.
  • Saure Lebensmittel Tabelle.
  • Strafe für Freier Corona.
  • MECE.
  • Steuern Kroatien.
  • Schönes Wochenende Post.
  • Haus kaufen Werl Mawicke.
  • Plauener Spitze Deckchen modern.
  • Mattel Cars 1 55.
  • Zehensocken Herren.
  • Abkürzung gegen.
  • James Arthur acoustic.
  • Tanzschule Visselhövede.
  • Geisterhaus Bad Wildungen.
  • Nintendo Switch rechter Joy Con funktioniert nicht.