I would like to use the MiniProfiler with MongoDB but it looks like
there is only support for the MongoDB Driver Version 1.9.0.
The current version of the MongoDB Csharp Driver is 2.0.1 and it has changed a lot.
Is there any workaround or fork on github available?
Related
we are trying to migrate to .net-core 3.0 from .net-core 2.2, is nhibernate fully compatible with .netcore 3.0 ?
Currently, we are using .netcore 2.2 and nhibernate is fully compatible.
As I know Nhibernate 5.2.3 is full compatible with .net core 3.0.
It seems Nhibernate 5.2.6 is same as 5.2.6.
https://gunnarpeipman.com/aspnet-core-nhibernate/
BR
I want to create ADO.NET entity data model - database first (.edmx file) with EntityFramework6.Npgsql but it's error. I have installed:
- EntityFramework6.Npgsql (version 6.3 newest)
- Npgsql (version 4.1.1 newest)
- EntityFramework (version 6.3 newest)
I created it before, but I don't know why now! Please help me....
This is a known issue that is already tracked on github
In the meantime for those having issues with the latest version of the
VSIX (4.1.1.2), please downgrade back to 4.0.x.
So downgrade your Npgsql version and extension version.
I just install meteor.js and try to use it replace the old frameworks.
The issue is:
On my windows 10 64bit system, the meteor is use 32bit mongodb(2.6.7), which is limited th database size is 2gb.
How to make the meteor work with 64bit mongodb?
Having researched this myself just now, it looks as though the Meteor version 1.4 release will be updated to version 3.2 of MongoDB, in which "32-bit binaries are deprecated"
Github ticket for the updating of MongoDB
MongoDB declaration that 3.2 has deprecated 32-bit binaries
Meteor 1.4 announcement
If upgrading your MongoDB instance is mandatory now, then unfortunately it looks like the only way is to manually upgrade the binaries yourself. If you do this, I would suggest you make a backup of them just in-case it messes up.
To upgrade to version 3.2 you first need to upgrade to version 3.0, then you can upgrade to version 3.2
I guess you didn't install the right version of Mongo if you have a 32 bits version.
check out their installation guide:
https://docs.mongodb.org/manual/tutorial/install-mongodb-on-windows/
First download the right 64 bits version for Windows:
https://www.mongodb.org/downloads#production
and follow the instructions:
Install MongoDB
Interactive Installation 1 Install MongoDB for Windows. In Windows
Explorer, locate the downloaded MongoDB .msi file, which typically is
located in the default Downloads folder. Double-click the .msi file. A
set of screens will appear to guide you through the installation
process.
You may specify an installation directory if you choose the “Custom”
installation option.
NOTE These instructions assume that you have installed MongoDB to
C:\mongodb. MongoDB is self-contained and does not have any other
system dependencies. You can run MongoDB from any folder you choose.
You may install MongoDB in any folder (e.g. D:\test\mongodb).
We are upgrading IBM Filenet Content Manager 4.5.1.
what version of Filenet and distribution recommended install. Is it the IBM filnet content manager version 5.1 or 5.2, based on stability ?
I am bit concerned beacuse of so many customizations and workflows running on our existing 4.5.1 system.
I'd recommend going to FileNet Content Platform Engine 5.2. I've recently completed an upgrade from 4.5 to 5.2, and no changes to any existing workflows or client code were required. There have been some additions to the API, but no breaking changes.
The latest fix pack, released a few weeks ago, is 5.2.0.3. I can't think of any advantage to going to 5.1 instead of 5.2.
I agree with cmaitchison. We have recently completed a 5.2 upgrade an it is straightforward. Even though the previous custom applications would work, it is better to re-compile using the latest libraries and the version of JRE your application server would use.
After quite some time developing with Oracle Client 9.2.0.7, and the ODP.NET to go with it, targeting .NET 1.1, we are upgrading our code line to .NET 3.5 and we are also considering upgrading the Oracle Client version.
I wonder if there are any "gotchas" as to whether specific versions should be used/not used?
For example Oracle Client 9.2.0.4 was known to be buggy with .NET and the upgrade to 9.2.0.7 was non optional.
Apparently the current Oracle Client version is 11.1.0.7.0 (from here). Has anyobody had specific issues with this version and would recommend other version? Sometimes installing the latest release isn't the best choice...
Take a look at the following document from Metalink, it might help. It contains a matrix of ODP Driver Version, Supported Operating System, SQL*Net, RDBMS, .NET Framework, and Visual Studio.
Subject: Oracle Data Provider for .NET (ODP) Supported Configurations
Doc ID: 726240.1
If all you need to do is talk to Oracle, then you can use my instructions found here for the Oracle 11 Client XCopy deploy.
The latest version is the only version that you can use if you have visual studio 2008 unless you don't want any of the snazzy add ins that Oracle provides with it (such as SQLPlus and such). I use the latest version to connect to a 10g database just fine.