Well no wonder, you first make it into base64, and then use that as raw bytes - that does not make any sense in any way.
If you want to use ReadAllBytes, then at least pass the bytes to the MD5 object as bytes. Or if you have to use base64, decode it first System.Security.Cryptography.MD5 has a ComputeHash which takes a Stream as argument.
Why you are converting the byte array into a base-64 string and then calculating the hash on the string? You can calculate the hash directly on the byte array, probably that is the reason because your hash in incorrect.
Also, why you are using Regex.Replace instead of the regular string.Replace?
For your 2nd problem, you can calculate the hash on a stream instead than on a byte array (that has a limit of 2Gb).
The following code summarizes what you have to do:
public static string MD5Hash(string filename)
System.Security.Cryptography.MD5 md5 = new System.Security.Cryptography.MD5CryptoServiceProvider();
using (Stream stream = new FileStream(filename, FileMode.Open, FileAccess.Read))
return BitConverter.ToString(md5.ComputeHash(stream)).Replace("-", "");
Luc Pattyn [Forum Guidelines][My Articles] DISCLAIMER: this message may have been modified by others; it may no longer reflect what I intended, and may contain bad advice; use at your own risk and with extreme care.
Please I need help on this problem.
I have an application am writing using visual c# 2008. The isuse is this I want connection string to the database to be read from a file save elsewhere on the system because after package and installation of the application if there is any changes in the connection parameter i will just change it in the file insted of changing it in the code and package it again. Onformload, he read the connection file and connect to database.
Did you ever heard of the App.config? Click on your project in VS, select "Add new element" and choose "application settings file" from the dialog. You can access the config with System.Configuration.ConfigurationManager.ConnectionStrings.
You must also encrypt your connection string before write it to a file.
You don't want anybody to know your database password, do you
You can't make it impossible. If you encrypt it, well, your program would contain the code to decrypt it. And they will have that code.
The same problem applies to all local data and is impossible to solve, though you could make the chain of encrypted keys of arbitrary length to slow the attacker down.
Edit (used to be something here about encrypted connection strings): scratch that, it's just impossible as well. Great. So now we know you don't even need to try to hide your connection string, at least that saves us all some effort.
I would use App.config aswell as SeMartens describes, but if you prefer to use a seperate file other than App.config, why not make the main program retrieve the connectionstring from a seperate class with a static method and just have that as a dll file. Then if the connectionstring should change you only have to replace the dll with a new one.
I am sending emails with attachment(.txt file) using c#.
I read data from database saved as varchar datatype. I read data in memory stream and output the memory stream as attachment with content type text(.txt file).
It sends emails to gmail, yahoo,hotmail,rediff etc. mail servers with attachment(which is a .txt file) perfectly fine.
(It means there is no problem with code)
But when i send emails to my own mail server it skips the attachment i.e. i get the emails without attachment.
Why make it worse by highlighting the fact he left his mail server IP address, not that it's anything important or useful to the outside world, it can be resolved with a DNS request. But either way, why repeat it and take attention to his error?
Why would they want to transfer the data to Access Do they realize there are reporting solutions that will work without the transfer. Or at least use SQL Server, Express is free and coupled with SSRS it would be better than Access, IMHO
You could do it with a datareader, transfer one record at a time.
Access can be a very good reporting tool but the problem with many Access users is that they tend to want to import the data into access and then report on it. Instead, you should create linked tables in access and then create parameterised queries on which to base the reports. Doing so will ensure that only the data you're reporting on gets copied temporarily into access
Last Visit: 31-Dec-99 19:00 Last Update: 27-Feb-21 18:09