Hi,
Is there anyway to load a PDF straight from a DB and not have to first create a file? I have it working loading a FileStream using your IStreamWrapper, but cannot get it to work using a MemoryStream straight from the Db using a byte array. Is this possible?
Thanks,
Jesse
Using MemorySteam from DB and not use a FileStream
Moderators: TrackerSupp-Daniel, Tracker Support, Paul - Tracker Supp, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Ivan - Tracker Software, Tracker Supp-Stefan
Forum rules
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
-
coblejesse
- User
- Posts: 34
- Joined: Thu May 16, 2019 7:44 pm
-
Sasha - Tracker Dev Team
- User
- Posts: 5522
- Joined: Fri Nov 21, 2014 8:27 am
- Contact:
Re: Using MemorySteam from DB and not use a FileStream
Hello Jesse,
If you want to implement the wrapper, the memory that you are using must be available for entire time while the file is open and the .Net manager is using the memory. Also, if you are using x86/Win32 build then you can run out of memory unexpectedly as you are using the .Net memory manager so try x64 just in case.
Also, we can't advice you anything more, until we see your code.
Cheers,
Alex
If you want to implement the wrapper, the memory that you are using must be available for entire time while the file is open and the .Net manager is using the memory. Also, if you are using x86/Win32 build then you can run out of memory unexpectedly as you are using the .Net memory manager so try x64 just in case.
Also, we can't advice you anything more, until we see your code.
Cheers,
Alex
Subscribe at:
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ