16,019,957 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Visual Basic questions
View Javascript questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by KevinAG (Top 5 by date)
KevinAG
31-Jan-11 17:40pm
View
Deleted
At another place I worked, this is the way we did it as well. At that job, we had four environments, development, functional test, beta, and production. Each environment typically had two "NCC" servers, two web servers, and a clustered database server. Our suite of applications used things like MSMQ and every custom service had to be redundant and work well with load balancing.
We then had a naming convention that we used for each server in each environment. dev-ncc1, dev-ncc2, dev-web1, dev-web2, ft-ncc1, ft-ncc2, ft-web1, ft-web2, beta-ncc1, etc...
This would allow for us to create appSettings keys like:
<add key="RefreshCacheIntervalSeconds" value="60"/>
<add key="[dev-web*]RefreshCacheIntervalSeconds" value="10"/>
So while developing, the RefreshCacheIntervalSeconds would have a value of 10, but everywhere else, it would have a value of 60.
This would also allow you to take things a step further and have:
<add key="[dev-web1]RefreshCacheIntervalSeconds" value="10"/>
<add key="[dev-web2]RefreshCacheIntervalSeconds" value="20"/>
<add key="[ft-web1]RefreshCacheIntervalSeconds" value="30"/>
<add key="[ft-web2]RefreshCacheIntervalSeconds" value="40"/>
if there was a setting that needed that kind of fine grained control.
KevinAG
18-Jan-11 12:26pm
View
Deleted
Thanks, Indivara. That is the correct string for the AllHtmlTagsPattern. I also just noticed that the snippet for the "...when pasting markup from Microsoft Word..." sample should be:
<!--[if !mso]> st1\:*{behavior:url(#ieooui) } <![endif]-->
KevinAG
17-Jan-11 20:48pm
View
Deleted
Damn, OK, I will try escaping out the whole string myself.
AllHtmlTagsPattern = @"</?\S+?((\s+[\S-[=]]+?(\s*=\s*(?:"".*?""|'.*?'|[^'"">\s]+))?)+\s*|\s*)/?>";
KevinAG
17-Jan-11 20:46pm
View
Deleted
Well, apparently CodeProject's parsing ate my code. The regular expression strings are obviously wrong. In the preview they were just fine. Let me see if I can write them here (I don't see a way to edit my post).
AllHtmlTagsPattern = @"\s]+))?)+\s*|\s*)/?>";
CommentTagsPattern = @"<![\s\S]*?--[\s]*>";
KevinAG
17-Jan-11 20:19pm
View
Deleted
Reason for my vote of 1
Not secure or robust. See alternative.