Skip to main content

IBM announced the beta release of its driver for Visual Studio 2010

After a really long waiting period, it’s finally there, a beta version of IBM’s .NET provider for .NET Framework 4.0 as well as Addins for Visual Studio 2010. This beta level package requires a V9.7 FP3a client install(available here:

http://www-01.ibm.com/support/docview.wss?uid=swg24028317) , and has the following features:
  • DB2 .NET provider for connectivity to DB2 LUW, IDS, DB2 for z/OS and DB2 for IBM i
  • DB2 Connect license required for z/OS and IBM i
  • Common IDS .NET provider for IDS
  • Entity Framework provider
  • Entity Framework support for database first scenarios
  • Entity Framework canonical function support
  • Full filtering of Add Connection properties when use with Entity Framework Designer
  • Visual Studio 2010 Addins
  • Full Server Explorer filtering support
  • Windows, Web and WPF application development scenarios with full drag and drop
  • Designer support for SQL Procedures with syntax highlighting
  • Full end to end debugging for SQL procedures for VB and C# apps
  • Schema evolution support for common developer focused tasks
  • Create database, create / modify table, view and change data
  • DB2 for z/OS V10 server supported
  • z/OS Enhanced timestamp precision and timezone support
  • z/OS Extended indicators
  • z/OS Currently committed isolation level
  • Informix Panther servers supported
  • Informix Stored procedure debugging
  • Informix Trusted context support
  • Near complete 3.5 canonical function support
  • Support for EF 4.0 canonical functions, above URL also includes 4.0 functions
  • CURSOR datatype supported for alternative result set processing

Here is the url for downloading the beta: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swerpdb2-datadv10-3

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more