The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
I have great pains. Our application consists of a launcher and various dlls.
The launcher looks at the fileserver for newer versions of the dll's and copies them over if required, then the main process is run inside the dll.
It works nicely, or should, and means that users always run the latest version. Win-win. Except.
When we copy over the files to the file server from the build server, one of the dll's is marked as from an 'unknown source' and is blocked. I could go into group policies and disable the blocking but that would be for any other dll/exe that should be blocked.
For now, after each update I have to manually unblock the file. Does anyone have an idea of a better solution?
I share your pain, I have an installer that 'updates' a certain dll to a version that was released when the earth was hot. The worst thing is that version of the dll doesn't have voodoo for the program to work...
I looks like I will be forced down the snake route, so as some one who has an ammount of Vis Studio experience (VB, VB.NET, C#) and a very solid background in C is there a route other than the Python for Beginners book I have gone through that basically give you an overview and simple examples rather than this is how you automate X with it. I mean I can write a text adventure, not automate things.