Guidelines for writing Articles on


* Please note that articles that involve guest posting with the the purpose of link exchanges/posting etc will not be considered. This is an educational website and the purpose is to spread knowledge and not to get involved in link baits.

Formatting Requirements

1. Please submit your articles in a Word document. Use this Template as a Starting point. It already uses the Title and Heading 1 styles.

2. Styles to breakdown various sections for example:

  • Title
  • Heading 1
  • Heading 2
  • Heading 3
  • Conclusion

3. Code should be inserted as text, not image/screenshot. Use the ‘Code’ Style from the Styles Gallery above

  • Use 9pt Font Consolas
  • After you paste code from code editor ensure line spacing is ‘Single’ and there is no un-necessary spacing at the beginning of the line. First line of code should not have any indent.

4. Screenshots should be relevant to what is being explained and should not exceed 700px width.

Content and Code

1. The content should be original work and unless it is a product showcase the Write up should be original.

2. You agree that you will not publish the content after submission or publication to any other blog/website/other medium. We need the website/magazine content to be exclusive to avoid duplication and adhere to search engine guidelines. However you can publish an abstract of the article with a link to the original article.

3. You provide DotNetCurry the permission to republish the article on the following umbrella sites viz. If reproduced, it will primarily be used for promoting the article.

4. Images should be in a separate folder and of .png format. They should be named well enough such that it’s easy to relate them to the article. Eg: an image that talks about json in Web API can be named as json-web-api.png. Observe the use of hypens (-) to separate words.

5. Please run a spelling and grammar check before you submit. Ignore code related spelling errors, but please ensure Method Names and variables have the correct spelling.

6. Try to start off with an Introduction and round off with a Conclusion type of section. Feel free to add other sections as required. An Abstract for the article is absolutely necessary to have.

7. We may request you for revisions or not publish the article immediately if we find it needs significant editorial intervention or has technical inaccuracies.

8. We don’t have a hard rule on the length. But we expect it to be between 1500 and 3000 words for magazine articles. Web Site articles can be smaller up to 800 words excluding code.

9. Once you have narrowed down on your article topic, please send us the Abstract.

10. If you have demo-able source code, once you send us the abstract we will create a private GitHub repository in which you can commit code. (This is Optional, you can send us the complete code in a zip too). The repository is made public once the article goes live.

Sample Code

1. Use Nuget packages wherever possible.

2. Enable Nuget Package Restore so that packages get downloaded automatically and you don’t have to commit the packages folder to github.

3. If you have dependency of a particular DB schema that is not generated by EF, please provide two scripts

a. Schema Generation script.

b. Sample Data population script.

What happens after we have received an article?

Once you have submitted an article, we will review your article, checking the content for accuracy. This process can take 3-5 days. Once the editorial process is complete, we will publish your article on our website.

Where do I send my article?

You can mail us your piece of stuff at writeforus[attherate]