if you delete the line and the code does not compile, then you need it. Or if you are using a plug-in like R# it will highlight the extraneous using statements, along with a plethora of other IDE goodness.
modify and release... never. you always want to test your application. the worst case is manually testing the changes (F5) and making sure the system works. A better solution is to create automated tests which you can execute and verify a majority of the system within seconds/minutes. you still need to manually tests, but the automation can ensure most of the system (especially business logic) is working correctly.
after testing locally, deploy to a test server/client. this will help work out the kinks with a true distinction between the client/server. during development your box is both the server and the client and it's easy for security and infrastructure bugs to masked.
after the application works in the testing environment you can deploy into production.
you should never deploy straight from your local development copy to production.
i say all that, but in the case of removing unused namespaces. if the code doesn't compile you cannot deploy, so tests, in the sense of automated or manual, aren't needed for this this specific modification. in general though, you should test your changes before deploying.
Also, comment out all using lines. IF your program needs the particular using line and it's commented out, you should get errors immediately. Uncomment what you need. After you've compiled/run/tested you app, you can go back and delete those commented lines.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.