Hide close button for Windows Form

In the windows form add this code

  protected override CreateParams CreateParams

       {
           get
           {
               CreateParams param = base.CreateParams;
               param.ClassStyle = param.ClassStyle | 0x200;
               return param;
           }
       }

Comments

Post a Comment

Popular posts from this blog

Architecture is about Intent.. My few cents..

Image
https://www.youtube.com/watch?time_continue=5&v=IEQr7gn6Gnc https://www.youtube.com/watch?v=o_TH-Y78tt4 https://www.arch2o.com/famous-architecture-quotes-time/ The Principles of Clean Architecture by Uncle Bob Martin Architecture is about Intent !  Its not about tools , Its not about frameworks , those are details, details should be hidden and not exposed.  It is vital to keep the business logic is kept immune the delivery model. Architects are abs-tractors, we separate details from general things. e..g UI or database is details Good architecture is allowed major decision to be differed. Job of an architecture is not to make decisions but to differed the decisions. Good architecture maximizes the number of decisions NOT made. Architects are responsible for Form and Structure while engineers are concerned with structure and functions. What activities an Architects do Act as a true trusted advisor & value-based professional. The solution ar...
Read more

Definition & Delivery of the software architecture

Image
Definition of the software architecture The architecture definition process seems fairly straightforward. All you have to do is figure out what the requirements are and design a system that satisfies them. But in reality it's not that simple and the software architecture role can vary wildly depending on how engaged you are and how seriously you view your role. As the following diagram shows, the architecture definition part of the role can be broken down further into a number of different elements. Management of non-functional requirements : Software projects often get caught up on asking users what features they want, but rarely ask them what non-functional requirements (or system qualities) they  need . Sometimes the stakeholders will tell us that "the system must be fast", but that's far too subjective. Non-functional requirements need to be specific, measurable, achievable and testable if we are going to satisfy them. Most of the non-functional re...
Read more