How much volume can the EVO HTML to PDF Converter for .net handle?
What specs do you recommend for the server?
I am unable to find information regarding this matter on evopdf.com.
The answer lies in chapter 3 of the the EVO HTML to PDF user guide, see the excerpt below.
3. Requirements and Recommendations
The recommended hardware and software resources for successfully running the EVO HTML to PDF converter for .NET are listed below. Basically this is the environment we used for testing the product.
Operating System: Windows XP, Windows 2003 Server, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012
Hardware Architecture: 32-bit, 64-bit (recommended to run the converter in a 64-bit process)
Free RAM: 2GB
Microsoft .NET Framework 2.0 or 4.0
Full trust level when used in ASP.NET applications
Related
Problem
I can't get 64-bit Word to load (or acknowledge the existence of in any way) an otherwise working Word VSTO add-in.
Discussion
I have a working Word VSTO add-in that I developed using Visual Studio 2017 on a 64-bit Windows 7 machine running Microsoft Office 32 bit. I use a WIX installer to deploy the add-in. I successfully deployed the add-in to a Windows 7 64 bit "master" gold disk that runs 32-bit Office, i.e., the add-in is available to any user who brings up a virtual desktop from the master gold disk. See Nova Sys Eng S.O. answer here for details.
Now, my organization is replacing Win 7 64-bit VDIs running 32-bit Office with Win 10 64-bit VDIs running 64-bit Office. In preparation for this, I created a 64-bit Win 10 development machine, installed Office 64-bit, Visual Studio 2019, the WIX Votive2019 extension, and the WIX toolset. On this development machine, I built a release version of the add-in and installed the MSI on this development machine. When I bring up Word on this development machine, it works fine.
Next, I carried the MSI built on the development machine to the 64-bit Win 10 master gold disk machine (again, running Office 64-bit) and successfully installed the add-in (i.e., the WIX installer finished without error). I also installed the VS 2010 Tools for Office Runtime (10.0.60828 released 2018) on the 64-bit Win 10 master gold disk machine. Just like on the 64-bit Win 7 master gold disk (Office 32-bit), the add-in was installed on the 64-bit Win 10 master gold disk machine in
C:\Program Files (x86)\FooAddIn
and the registry settings are
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\Word\AddIns\FooAddIn]
"FriendlyName"="Foo Add-In"
"Description"="Foo Word Add-In"
"Manifest"="C:\\Program Files (x86)\\FooAddIn\\FooAddIn.vsto|vstolocal"
"LoadBehavior"=dword:00000003
When I bring up Word on the 64-bit Win 10 master gold disk machine, the add-in does not load because, apprently, Word is unaware of its existence, i.e,. when I look at Word Options -> Add-Ins, the add-in is not present at all. When I select COM Add-ins -> GO, the COM ADD-ins dialog also does not show the add-in.
One more item:
On the development machine, the Build Config Manager look like the following, i.e., the Platform for the WIX installer program (FooAddInSetup) is set to x86, and there are no other options available.
Why won't Word acknowledge the existence of my add-in?
Is the fact that the add-in is installed in Program Files (x86) an issue?
Is the fact that the Platform for the WIX setup program is x86 an an issue?
I stumbled across Addins for Office programs may be registered under the \Wow6432Node. The part that helped me is this:
Even though I built the add-in on a 64-bit machine that has 64-bit office, the WIX installer set things up such that when I ran the MSI on the Win 10 64-bit gold disk machine (that has 64-bit Office), it added the reg settings to the HKLM\Software\Wow6432node as though the machine has 32 bit office.
I manually created the same reg key settings under HKLM\Software\Microsoft, and the add-in loaded just fine.
So, I have to figure out what I need to do to the WIX config settings to make it right for a machine that has 64-bit office on it.
BTW, the Microsoft page Registry entries for VSTO Add-ins seems to have it backward:
I'd like to install MongoDB Community Edition on my computer, which has the 64-bit Windows 10 Home OS, but the system requirements say I need Windows Server 2008 to do it.
I don't think my computer has Windows Server 2008. Is there any way around this? For example, would it work for small-scale databases, or is it totally incompatible without Windows Server 2008?
If I absolutely can't use MongoDB, is there another non-relational database that would work with my system? (It would have to be free.)
I admit that the download site is a bit confusing.
But you can simply download the MSI and install it on your Windows 10 machine. A Windows Server version is not required for the community edition.
Disclaimer: I have it on a Pro (Windows 7 and 10, without Windows 2008 or any other server) edition, not on a Home edition, but I'm pretty sure that it will work in the local machine context)
I've installed Google Web Designer on Windows XP, and saw this error:
The procedure entry point GetSystemDefaultLocaleName could not be located in the dynamic library KERNEL32.dll
What can I do?
I think that it won't support XP.
Here are the minimum system requirements, according to their documentation:
Operating system
Windows requirements
Windows 7
Windows 8
I think it does not support Windows XP. I installed in Windows 7. No issues. The error you have got is mainly caused by misinterpreted operating system -- that's described as a possible cause in Microsoft's support knowledge base:
The application is misinterpreting the operating system version and is trying to call a procedure in the Windows 95 or Windows 98 version of the Dynamic Link Library (DLL) that is unavailable in Windows NT version 4.0 or Windows 2000.
Windows XP is not supported. See the system requirements.
What are the basic system requirement for installing asp.net mvc 2 application.
Edited:-
If I want to host the asp.net mvc 2 application on the windows XP then is there any special requirement like IIS version, Framework, service packs or else ?
AS per the MVC download page, any of the following operating systems:
Windows Server 2003,
Windows Server 2008,
Windows Vista,
Windows XP
Required framework:
.NET 3.5 SP1 Framework
As per the framework download page, it has the requirements:
Processor:
400 MHz Pentium processor or equivalent (Minimum)
1GHz Pentium processor or equivalent (Recommended)
RAM:96 MB (Minimum); 256 MB (Recommended)
Hard Disk: Up to 500 MB of available space may be required
I have basically succumbed to the fact that if you are a hardcore computer user, you will have to reimage your computer every few months because something bad happened. Because of this, I bought imaging software and then really got into imaging. I am now ready to move my development environment completely into a virtual machine so that I can test sites on IIS as though I am on a dev network (and backup these images easily).
The question is, what is the best virtual development platform for a 4 gb laptop? A virtual Vista Business with 3 gb of ram, windows XP sp3 with 3 gb of ram, or Windows Server 2003 with 3 gb of usable ram.
Tools I will need to install:
*sql server 2005 dev edition
*vs 2008 sp1
*tools for silverlight
*and multiple other smaller testing tools
I have tried the following combinations:
Windows XP SP3 on Virtual Server
2005 R2
Windows Vista Business
x64 on Virtual Server 2005 R2
Windows XP on Virtual PC 2007
Windows 2003 on Virtual Server 2005
R2
Windows XP on VMWare Fusion
and the Virtual Server installations where either local or hosted on a server and they all ran fine and about the same speed.
The VMWare Fusion Virtual Machine running under OS X is (seat of the pants) significantly faster than the others. I haven't tested VMWare on Windows to see if it is VMWare or the Hardware making the difference, but it's something worth looking into.
Server 2008, converted to a workstation.
Nothing compares IMO, I've loaded 3 Different OS's in the last 3 months, and I'm set on Server 2008.
I think the biggest question (from my standpoint) is whether or not you'll be doing development (like SharePoint) that requires a server platform. If you anticipate a lot of SharePoint development (or perhaps Exchange, or BizTalk, or another product that requires development be done on a server platform), then go with Windows Server 2003. If not, then I'd probably choose XP, though Vista isn't a bad development platform.
I personally prefer developing on a server platform - however, that opinion might shift if I was developing any sort of WinForms applications, since it would more correctly represent the OS family for the target audience.
I did notice a slight performance decrease going from Server 2003 to Server 2008 that I was not expecting, but that might be more from doing an in-place upgrade instead of starting clean.
From the options you gave, I would personally go with W2k3. You can really trim a server OS down to run lightning-fast, especially when you don't have or get rid of the MS "eye candy".