---
title: "Developing as non-admin made easier with VS.Net 2005?"
url: "https://osherove.com/blog/2004/12/29/developing-as-non-admin-made-easier-with-vsnet-2005.md"
canonical: "https://osherove.com/blog/2004/12/29/developing-as-non-admin-made-easier-with-vsnet-2005.html"
published: "2004-12-29T14:10:00"
updated: "2004-12-29T14:10:00"
tags: [".Net Original"]
author: "Roy Osherove"
description: "One of the coolest things about VS.net 2005 is that you can actually debug your application using specific \"Click-Once\" security permissions. Simply go into the \"properties\" of your project, click the \"Security\" tab,…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Developing as non-admin made easier with VS.Net 2005?

By Roy Osherove December 29, 2004 In [.Net Original](https://osherove.com/blog/category/net-original)

**Historical article** · Originally published December 29, 2004; technical details may be outdated.

One of the coolest things about VS.net 2005 is that you can actually debug your application using specific "Click-Once" security permissions. Simply go into the "properties" of your project, click the "Security" tab, and set the "Enable ClickOnce security Settings" checkbox to true.

ow you can decide under which permissions your application will run.

An interesting thought this brought on - does this rid you of the "Develop as admin" problem? Can I from now on develop as admin, but use this setting and still make sure least privileged users can run this securely?

I wonder..

## More in .Net Original

[All posts in .Net Original](https://osherove.com/blog/category/net-original)

- Dec 29, 2004

    ### [Do not serialize delegates and events blindly](https://osherove.com/blog/2004/12/29/do-not-serialize-delegates-and-events-blindly.html)

- Dec 29, 2004

    ### [Denying your public classes from your end customers](https://osherove.com/blog/2004/12/29/denying-your-public-classes-from-your-end-customers.html)

- Dec 14, 2004

    ### [Session ideas and suggestions for Microsoft Tech-Ed 2005 and future conferences in general](https://osherove.com/blog/2004/12/14/session-ideas-and-suggestions-for-microsoft-tech-ed-2005-and.html)

- Dec 13, 2004

    ### [.Net Deep dive lecture videos online](https://osherove.com/blog/2004/12/13/net-deep-dive-lecture-videos-online.html)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/