Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
It’s extremely easy to create new Sitefinity widgets by creating a new ASP.NET control. However, sometimes this custom code doesn’t work well in Sitefinity’s Page Editor. In those cases it becomes necessary to disable the offending code while working in Sitefinity’s design mode.
To do this, we need to know whether the page is running in Page Edit mode. Thankfully, there are a couple of a handy extension methods that enable us to determine if Sitefinity is switched into design mode (or preview mode).
// If working in an ASP.NET Control... if (SystemManager.IsDesignMode)
// If working in an ASP.NET Page or Master Page if (this.IsDesignMode())
It should not be necessary to add any namespace to utilize this code. Just be sure to use the appropriate code for the appropriate setting (controls vs. pages). The actual code for disabling functionality in these modes will need to be inserted into the code blocks above.
If you’re looking for more information, check out the following resources:
Happy coding! :)
View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.