+972 52-548-6969
The following is NHProf’s Main method:
Each of the currently existing conditions (and I am pretty sure that they will grow) is there because of bug reports from the field.
It gets… interesting, sometimes, the things that user do to my poor app.
Markdown turns plain text formatting into fancy HTML formatting.
*italic* **bold**
_italic_ __bold__
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Three or more dashes or asterisks:
---
* * *
- - - -
End a line with two or more spaces:
Roses are red,
Violets are blue.
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowTerm 1
: Definition 1
Term 2
: Definition 2Body text with a footnote [^1]
[^1]: Footnote text here
MDD <- will have title
*[MDD]: MarkdownDeep
No future posts left, oh my!
| Main feed | |
| Comments feed |
Comments
Yeah it's a much different world than corporate clients that's for sure. The precautionary steps required are ten-fold in order to prevent an avalanche of false positive bug reports and associated problems.
I say, bind 'em up and lock 'em down. If your product still runs then your user will have a pleasant experience and be grateful to you, otherwise barf early and often otherwise the user will falsely cuss you like they do Microsoft.
I don't think you should do that - simply close the app without any notification for the user.
You should output a message telling a user why you are closing.
Krzysztof,
The Assert is also responsible for alerting the user
Ayende, not surprisingly, at the early stage of NDepend I wrote a similar post. But we try to go further by making sure all assemblies are here with all correct version in all correct location:
codebetter.com/.../...tallation-in-production.aspx
Yip, I've done similar assertions, as well as doing permission assertions.
e.g. Try running NHProf under Intranet/Internet Zone policies.
Hmm wouldn't reflector + deblector + reflexil make it trivial to bypass this? or i'm missing something?
Set,
Please read it.
Then guess about why I need it
Ahh nevermind i thought it was some kind of assert to "protect" your files in addition to your licensing scheme. I should go to sleep :x
I wouldn't bother at all to be honest. If someone is going to delete files I would let the app crash.
Maybe the unhandled exception dialog could suggest re-installing the file and if the problem persists they should send the bug report on to you.
Peter,
You do realize how many support calls a good error can save you?
Oren - yes I do realise how many support calls a good error can save :-)
mrpmorris.blogspot.com/.../...ance-of-clarity.html
So you realize why it is important to try to reduce them :-)
Comment preview