|
There are articles on audio recorders here on CP.
Try searching the multimedia zone.
Regards,
mav
|
|
|
|
|
Hi,
Yesterday I found an application on the Internet that claimed that it managed to browse the source of any .NET application. In curiousity I downloaded it, installed it and tried to view the source of one my projects. Surprisingly it worked.
... which isn't too good!
Professionally it has to be impossible to work with a language that everyone can decompile after it's compiled! How do you do to protect your applications? Is there any methods that prevents this horrible feature? And why did Microsoft implent such redicilous feature?
// Zanathel
|
|
|
|
|
What you need is an Obfuscator for you code. Search for it on Google you will find more then enough information about them out there.
|
|
|
|
|
It's not a ridiculous feature, but an unfortunate side-effect of using an intermediate, hardware-independant language that all managed code is compiled into. The .NET Framework, at execution time, then takes that code, called MSIL, and translates it into instructions that the processor can actually execute.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Zanathel wrote:
Surprisingly it worked.
Not really. There is a little app that comes with the .NET framework that will do this also. It won't show you the original C# like some applications, but it will show the MSIL which, for the most part, can be easily read and understood.
Zanathel wrote:
Professionally it has to be impossible to work with a language that everyone can decompile after it's compiled!
Even C and C++ can be decompiles after it is compiled. That is why software licenses have had for many years a thou shalt not reverse engineer clause in them. While it is more difficult with a C or C++ application (because it doesn't have any metadata) it is still possible.
Zanathel wrote:
And why did Microsoft implent such redicilous feature?
The feature is not being able to reverse compile the application per se, but so that features such as reflection can work. This can be a very powerful feature which can make development a lot easier.
My: Blog | Photos | Next SQL Presentation
WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More
|
|
|
|
|
Zanathel: could you give the link to this decompiler? I'm really curious how it works!
|
|
|
|
|
|
|
I've got a string
@"\fs17 someTextHere\"
where 17 could be any number
I'd like to extrract the "someTextHere" part from the string using a regular expression.
The regular expression
@"\\fs(\d{1})+ (\w|\W)+\\"
will match the entire string; but I only want to find out the "someTextHere" part of the string. Could any of the regular expression experts here help me out?
Tech, life, family, faith: Give me a visit.
I'm currently blogging about: The Secular Left, the Religious Right, and Prejudice
Judah Himango
|
|
|
|
|
@"\\fs\d+ (\w|\W)+\\"
Now you have only one grouping, which is the word. You can get this group out of your regex match, it has a property or something to access it. Any bracket will generate a group. From memory, the array is 1 indexed, with the 0 index containing the whole match.
Christian Graus - Microsoft MVP - C++
|
|
|
|
|
Thanks Christian; I was totally oblivious to the groups property, much appreciated. For the record, I ended up modifying the pattern a bit:
<br />
@"\\fs\d+ (\w+|\W+)\\"
As the previous one grouped only a single character (the plus sign was outside the parentheses).
Tech, life, family, faith: Give me a visit.
I'm currently blogging about: The Secular Left, the Religious Right, and Prejudice
Judah Himango
|
|
|
|
|
Judah Himango wrote:
As the previous one grouped only a single character (the plus sign was outside the parentheses).
Sorry, I just copied that bit from yours, I didn't really check it 
Christian Graus - Microsoft MVP - C++
|
|
|
|
|
|
|
how can i have the computername in a simple windows application with c#
thanks
prog
|
|
|
|
|
I am assuming you are asking how you could get the computer name in a simple windows app? You could query the WMI for the computername.
Eric
|
|
|
|
|
For a much easier method, you'll find the computer name in the MachineName property of the Environment class.
String computerName = Environment.MachineName;
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
is it possible for this to be done for application running in a terminal services environment..can the name of the computer that is connecting to the app via terminal services be captured??
Afzal Hassen
|
|
|
|
|
Not that I know of. Since the application is always running on the server, it'll always return the name of the server. It has no way of knowing that it is running under a TS session since the .NET Framework doesn't expose any of the TS functionality. You'll have to look into calling the TS API directly to see if you can get the name of the computer that started the session.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
i have dabbled with the WTSQueryUserConfig API call,and it does return the name of the computer, thanks for that input...
would you by any chance know how i can access the client computer hardware information via TS?? or of any articles that can help me accomplish this??
Thanks
Afzal Hassen
|
|
|
|
|
TS doesn't care about the client hardware at all, so it's not going to give you access to it. But, there's always one of these, once you get the client computer name from WTSQueryUserConfig, you can use it to connect back to the client machine and query WMI (if available!) to get its hardware details.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
thanks
|
|
|
|
|
I am new to C#..about 6 months in. I am working on a program that will Inventory computers, and then either write out to a text file or dump the data into an SQL server. Would this be best suited to run as a Service or make it a scheduled task?
Eric
|
|
|
|
|
Scheduled Task. I did something like this a few years ago. But, I did it as a three part application.
First, the Client side. A small application, written in C++, that gathered everything I needed to know about each workstation at Login time. This app was launched out of a Novell login script and dumped all of its information into a common text file on the server. Each of the workstations generated a GUID for itself (only once!) and tagged it's data with the GUID. All the workstations at a site dumped its data into the same text file. Since each workstation was tagging its data with its own GUID, every workstation could repeatedly dump its data into the text file without worrying about getting counted multiple times. 40,000 workstations did not allow for me to write something to go out and "touch" each of the workstations from a central point.
Second, the Server side. Two parts. One was an SQL database that ultimately stored all the information on each machine. The Primary Key to this little table was, you guessed it, that little GUID that each machine generated for itself. Now, the second part of this was Collection application that went out to each server (200+) every night (scheduled task!), renamed the log file to a temporary name, then read the file line-by-line. If the GUID in the line was not already in the database, a new record was created using the new GUID. If the GUID was already in the database, it simply updated the record that was there. Now, you're probably thinking if I change out a machine and it gets a new GUID, what happens to the old record? Each record is stamped with the last date/time that that particular record was touched, either created or updated. The SQL Server ran a little statement that selected the records that have not been touched in the last, say 7 days. Old records are now either refreshed from the log file download, or are dropped. After the entire log file was read, it was deleted.
Third, the Reporting side. A simple data driven website using the SQL database as a backend.
Easy!
Now, why didn't I just have the Client app go directly to the SQL Server? Two reasons... Minimize the traffic going acrossed the WAN during the two busiest shifts of the day. And, the client machines were running various versions of Windows. Most of which either had screwed up SQL Server drivers or were behind firewalls that wouldn't allow that kind of traffic to get out.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Thanks for this Reply! I like the idea of writing everything to a text file first and then running an app from the server to enter the data into the DB. How could I go about getting the GUID with C#, and I am not familiar with adding records to a DB by reading from a file.....
Eric
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
