5 ms·

Yeah, we have issues with SSRS and Crystal Reports in cross-browser environments. i.e. the "preview" never looks like what you intend. Instead, we work around i

by cpher 14y ago

Yeah, we have issues with SSRS and Crystal Reports in cross-browser environments. i.e. the "preview" never looks like what you intend. Instead, we work around it by exporting directly to disk, which seems to keep the WYSIWYG aspect. I'm more interested to know how MS people have integrated PostGres into their environments. Which ORMs work? What are the gotchas, etc?

hp50g 14y ago
Nhibernate. No issues. To be honest we're shifting to java. Our license fees are well into 7 figures for MS stuff for no gain. This is the first step. Some subsystems are moving from asp.net web forms+mvc to spring, tomcat, hibernate, postgres. Cost savings are huge, staff available are orders of magnitude better and reliability is higher as to be honest, windows has been a piece of shit to manage over the last 10 years. Fortunately we've got a pretty well designed system so we can move it over piecemeal as and when we update major subsystem features.
- tracker1 14y ago
  Wow, my experience has been a bit different. Every Java project I've worked on has been an exercise in frustration... Though a lot of the .Net projects I've worked on I can say the same. I think that NodeJS + MongoDB has been the least resistance I've seen so far... though some of its' limitations are really frustrating (non-indexed result limitations). I like Postgres at least as much as MS-SQL Server. And the Entity Framework generators have been close to a blessing. That said, I'm much more of a fan of the DB as dumb storage, and not a big fan of SSIS. So changing from one DB to another is mostly transparent when things are how I prefer them.
- cpher 14y ago
  Well, we can't shift to Java--we're consultants. We're a total MS and esri (GIS) shop. I was hoping for some hints that ASP.NET could integrate smoothly w/ PostGres in order to offer something else to clients.
HarshaThota 14y ago
PetaPoco (http://www.toptensoftware.com/petapoco/ http://www.toptensoftware.com/petapoco/) and ORMLite (https://github.com/ServiceStack/ServiceStack.OrmLite https://github.com/ServiceStack/ServiceStack.OrmLite) both work with Postgres.
- cpher 14y ago
  I've looked at PetaPoco and Massive as a replacement for Linq2Sql, etc but don't know what experience others have had with it. We're mostly a MSSQL shop, but are seeing more Oracle projects. And now that PostGres is becoming stable in our GIS environment I'd like to know how people are dealing with multiple DB backends. Have you built anything in production with PetaPoco?
  - avenger123 14y ago
    I would really recommend you check out Llblgen Pro. The name is just weird but its a really good ORM. The support it has for all the major databases (SQL Server, Oracle, Postgres) and others is really solid. Also, there is a full Linq provider that works well.
avenger123 14y ago
I also think LLBLGEN PRO (http://www.llblgen.com/ http://www.llblgen.com/) is highly underrated. There are commercial providers but npgsql- http://npgsql.projects.pgfoundry.org/ http://npgsql.projects.pgfoundry.org/, works well.
- sitharus 14y ago
  As someone who works on a project that extensively uses LLBLGen Pro I'd have to disagree with you.
  - avenger123 14y ago
    Would you mind elaborating on this a bit? I would love to hear about it. I understand that some people get turned off by the code generation aspect of it, but what in particular didn't you like about it.
pbz 14y ago
I would recommend BLToolkit (and the newer lighter version Linq2Db -- not to be confused with Linq to SQL). You keep an abstraction level above raw SQL via LINQ and with multiple DB providers you can easily switch between databases without rewriting your queries (provided you don't use any DB-specific features).
taude 14y ago
Check out the lightweight ServiceStack postgres ORM for light-weight usage, consider it more on par featurwise with Linq2SQL: http://nuget.org/packages/ServiceStack.OrmLite.PostgreSQL http://nuget.org/packages/ServiceStack.OrmLite.PostgreSQL Edit: just noticed someone posted this below. Sorry.

by cpher 14y ago

hp50g 14y ago

Nhibernate. No issues. To be honest we're shifting to java. Our license fees are well into 7 figures for MS stuff for no gain. This is the first step. Some subsystems are moving from asp.net web forms+mvc to spring, tomcat, hibernate, postgres. Cost savings are huge, staff available are orders of magnitude better and reliability is higher as to be honest, windows has been a piece of shit to manage over the last 10 years. Fortunately we've got a pretty well designed system so we can move it over piecemeal as and when we update major subsystem features.

tracker1 14y ago
Wow, my experience has been a bit different. Every Java project I've worked on has been an exercise in frustration... Though a lot of the .Net projects I've worked on I can say the same. I think that NodeJS + MongoDB has been the least resistance I've seen so far... though some of its' limitations are really frustrating (non-indexed result limitations). I like Postgres at least as much as MS-SQL Server. And the Entity Framework generators have been close to a blessing. That said, I'm much more of a fan of the DB as dumb storage, and not a big fan of SSIS. So changing from one DB to another is mostly transparent when things are how I prefer them.
cpher 14y ago
Well, we can't shift to Java--we're consultants. We're a total MS and esri (GIS) shop. I was hoping for some hints that ASP.NET could integrate smoothly w/ PostGres in order to offer something else to clients.

HarshaThota 14y ago

PetaPoco (http://www.toptensoftware.com/petapoco/ http://www.toptensoftware.com/petapoco/) and ORMLite (https://github.com/ServiceStack/ServiceStack.OrmLite https://github.com/ServiceStack/ServiceStack.OrmLite) both work with Postgres.

cpher 14y ago
I've looked at PetaPoco and Massive as a replacement for Linq2Sql, etc but don't know what experience others have had with it. We're mostly a MSSQL shop, but are seeing more Oracle projects. And now that PostGres is becoming stable in our GIS environment I'd like to know how people are dealing with multiple DB backends. Have you built anything in production with PetaPoco?
- avenger123 14y ago
  I would really recommend you check out Llblgen Pro. The name is just weird but its a really good ORM. The support it has for all the major databases (SQL Server, Oracle, Postgres) and others is really solid. Also, there is a full Linq provider that works well.

avenger123 14y ago

I also think LLBLGEN PRO (http://www.llblgen.com/ http://www.llblgen.com/) is highly underrated. There are commercial providers but npgsql- http://npgsql.projects.pgfoundry.org/ http://npgsql.projects.pgfoundry.org/, works well.

sitharus 14y ago
As someone who works on a project that extensively uses LLBLGen Pro I'd have to disagree with you.
- avenger123 14y ago
  Would you mind elaborating on this a bit? I would love to hear about it. I understand that some people get turned off by the code generation aspect of it, but what in particular didn't you like about it.

pbz 14y ago

I would recommend BLToolkit (and the newer lighter version Linq2Db -- not to be confused with Linq to SQL). You keep an abstraction level above raw SQL via LINQ and with multiple DB providers you can easily switch between databases without rewriting your queries (provided you don't use any DB-specific features).

taude 14y ago

Check out the lightweight ServiceStack postgres ORM for light-weight usage, consider it more on par featurwise with Linq2SQL: http://nuget.org/packages/ServiceStack.OrmLite.PostgreSQL http://nuget.org/packages/ServiceStack.OrmLite.PostgreSQL Edit: just noticed someone posted this below. Sorry.