BinaryStream | Best replacement

You must decode hex string first.

After getting corresponding raw value, you can convert it to Base64 string.

EDIT:

Based on your comment, I realize that what you initially wanted was to keep the information about the character encoding inside the file without having a BOM.

The problem with this question (as you realized it) is that the BOM is actually what normally contains the information about the character encoding and putting this information anywhere else in the file doesn't really make sense.

So, your code is actually perfect for the task at hand. What needs to be changed is how the CSV file is imported/opened by the software you want to use.

When the file has no BOM, a software reading the file has to guess the character encoding.

In general, if the software you use doesn't support BOM and doesn't guess correctly, there should at least be a way to customize the behavior of the import/open command so that you can specify the character encoding (seems like you actually found it).

Original answer:

For some reason, Excel has a hard time to guess the character encoding when opening a UTF-8 encoded CSV file when you just double-clicking the file. You have to help it a little...

Instead of opening it directly, you could load the CSV content to a new workbook by using the (legacy) Text Import Wizard and selecting the UTF-8 character set (65001) during import if Excel is not able to figure it out by itself.

If you were to record a macro while doing it and make it into a sub procedure, you could have something like this:

These methods are hitting an issue where the bitwise operators are only working in 32-bit, so the 64-bit numbers are being truncated before your serialisation.

You can work around this with BigInt.

Japanese Code Page: From this blog entry: "Binary Files and the File System Object Do Not Mix": "In the Japanese code page, just-plain-chr(E0) is not even a legal character, so Chr will turn it into a zero... Do not use the FSO to read/write binary files, you're just asking for a world of hurt as soon as someone in DBCS-land runs your code."

Alternatives? How about .NET? I realized too late that you are in a custom action, I made the samples as standalone .NET console applications. The WiX framework has mechanisms to create a DTF custom action. Found this on github.com.

Rehashing?: Can we ask what you are actually doing? Why do you need to extract files this way? There could be other approaches that are more reliable if you explain the scenario?

DTF / .NET: Though I am not a huge .NET fan for deployment use (too many layers of dependencies), I think you would do better using .NET / DTF for this. What is DTF?

Sample DTF C# Application: Below is a simple, C# sample application showing one way to extract a binary stream from the Binary table (there are several other ways, I am not a .NET expert).

1. Create a new C# Console App (.NET Framework).
2. Paste the below code in and adjust parameters.
3. Add reference to Microsoft.Deployment.WindowsInstaller.dll (DTF framework).

The Base64Encode function was putting a line break in the output string, something I didn't notice until I response.write the output and looked at the source code of the page instead of the compiled page.

Always remember to look at the raw data, not just the displayed data (i.e. not like me)

MSChart is a nice control but unfortunately Microsoft has always failed to properly document it.

And with the latest changes at MSDN things have gone from bad to worse, so I can't actually point to the rules that go for the various ChartTypes.

In your case I deduct this (rather wacky) rule:

To attach a non 100%-series to an indepently scaled secondary y-axis it must be the first series but the stacked series still must be added first.

So, if you want to get a result like this:

..you need to adapt the code. Here are the changes and additions needed..:

First we have to insert the line series at the front but do that after the stack100 series have beeen added..:

I solved my own problem. I'm not 100% confident this is the best way to accomplish this, so I'm open to suggestions.

I made a subclass of stream.Transform and implemented the _transform method. I discovered that the next data chunk only gets input when the _transform callback is called. Knowing this, I stored that callback function as a property and only call it when I need the next chunk.

getBytes(size) is a method that will get a specified number of bytes from the current chunk (saved as a property as well) and call the earlier saved callback if the next chunk is needed. This is done recursively to account for varying sizes of chunks and varying number of requested bytes.

Then with a mix of async/await and promises, I was able to keep this entire process asynchronous (afaik) and backpressured.

I found solution for your problem, use options while creating file object as below

According to the docs, you have to allocate a buffer and return its address in the open's Buffer parameter (you need to change it into a ByRef parm for that!). Then you'll get that same buffer ptr passed in the other functions.

Ideally, you'd set