I have had a website up and running for over 3 years with SAP .net connector 3.0 in 32 bit format. Unfortunately the Windows 2003 server that was hosting this application has failed. Our network team has created a new Windows 2012 server, and request the website be re-written in 64 bit. I have successfully added the reference to the x64 version of sapnco dll's, but now when I try to compile website, I'm getting an error on my page directive.
The error is "ASP.NET Runtime error: Object reference not set to instance of an object"
None of the code itself (ECCDestConfig.vb and code behinds) does not show any errors. This error is appearing on the page directive of ALL my .aspx web pages in this project, even pages that don't call SAP.
I have set the configuration manager to use x64 as the active solution platform.
I am really stuck - and could use some help.
SAP .NET Connector needs Microsoft Visual C++ runtime of a specific version, which depends on both the .NET framework version and the version of the Operating System (32-bit or 64-bit).
According to the SAP official documentation, you need one of the followings:
NCo 3.0 32-bit (x86), .NET 2.0 (also 3.0, and/or 3.5): Microsoft Visual C++ 2008 Redistributable Pack (x86) (mscvp80.dll)
NCo 3.0 64-bit (x64), .NET 2.0 (also 3.0, and/or 3.5): Microsoft Visual C++ 2008 Redistributable Pack (x64) (mscvp80.dll)
NCo 3.0 32-bit (x86), .NET 4.0: Microsoft Visual C++ 2010 Redistributable Pack (x86) (mscvp100.dll)
NCo 3.0 64-bit (x64), .NET 4.0: Microsoft Visual C++ 2010 Redistributable Pack (x64) (mscvp100.dll)
Problem solved. I used VB in Visual Studio 2013 with the 64 bit SAP .nco . The problem was I had created a "website" not a new "project. Once I did, and loaded the SAP DLL's as references to the project, and changed the configuration to use x64, new web pages I added did so without error. I might note, I aslo installed SAP GUI 730 on the same server. Its working now, both interacting with SAP and a separate SQL database,
Thanks for your answer
To be able to execute the x64 dlls in VStudio, it must be verified that the project is being compiled also in x64. You have to go to Tools, Options ..., Projects and Solutions, Web Projects. And check "Use the 64 bits."
Related
Our continuous integration machine is using CruiseControl.Net and is running on XP Pro SP3. We're currently building x86 solutions in VB.NET from from VS2012 IDEs using the MSBuild.exe found in C:\Windows\Microsoft.NET\Framework\4.0.30319.
We had no problems until recently when code was recently added in one of the VS2012 solutions declaring a function that uses the Iterator keyword (as in Public Iterator Function (...)) and now MSBuild spews out a long list of errors for the declaration line. My understanding is that the Iterator keyword is newly supported for VB.net. Do we need an update for MSBuild or the VB compiler or something to get this to build on an XP machine?
[edit] Just noticed the VB compiler on the dev machines is v11.0.50938.18400 while the version on the integration machine is v 10.0.30319.233. I'm guessing that points to the problem. Next question: how do I get (or can I get) the 4.0 framework with the v11 compiler on to the cruise control machine running XP?
http://msdn.microsoft.com/en-us/library/hh162058.aspx
What's New in MSBuild 12.0 ?
MSBuild is now installed as part of Visual Studio rather than as part of the .NET Framework. The current MSBuild version number is 12.0. If you want to install MSBuild separately, download the installation package from MSBuild Download.
http://www.microsoft.com/en-us/download/details.aspx?id=40760
I'm not a big fan of this (moving it from the framework install). But it is what it is.
But you have an issue now.
Supported Operating System :
Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
I am getting a few errors trying to download the new VS2012. Its a fresh install of windows 8 (did the windows update). I have tried not selecting all (no C++, lightswitch, blend, office tools)
I tried different mounting tools for the .ISO but no luck. VS2010 is still working. Running x86. Log file
Errors:
Critical: Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.507 Cannot find the requested object.
Microsoft Visual Studio 2012 Pre-Clean Tool Cannot find the requested object
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.507 Cannot find the requested object.
Microsoft Visual C++ 2012 Core Libraries, Team Foundation Server 2012, Microsoft Framework 4.5 Multi-Targeting pack.... and a few other ones cannot be found. Thanks!
Downloaded the web installer, and that seemed to work. It seems that the iso was corrupted as the MD5 did not match.
I just installed VS 2012 Ultimate RTM on Windows 8 Pro RTM and tried to open a solution containing several projects (class libraries and WinForms) targeting .NET 4.0.
When the solution is loaded, VS prompts that .NET 4.0 isn't supported. It gives me the chance to update my projects to 4.5 (and promises that I could change the target later) or install a "Multi targeting pack" for 4.0 from this page.
I decided to update my projects to 4.5 because I had no luck installing the offered Multi targeting pack (errors see below).
Unfortunately, VS does not show 4.0 as a target by default (when changing the target for an updated project), but redirects me to the page where I can download the Multi targeting pack.
So far so good, but I wasn't able to install any of the offered downloads (neither runtime nor targeting pack) again.
The error message says in case of .NET Framework 4.0.3 Targeting Pack:
Setup has detected that this computer does not meet the requirements to install this software. The following blocking issues must be resolved before you can install KB2600213 software package.
Installation Requirements:
Microsoft .NET Framework 4 Multi-Targeting Pack was not found. Please repair your installation for Microsoft Visual Studio 2010 in order to get this update.
Strange enough since I have no VS2010 installed.
.NET Framework 4.0.3 Runtime Installation stops with the following error:
KB2600211 does not apply, or is blocked by another condition on your computer.
I've checked that .NET 4.0 is installed (using the .NET Installation verification tool), I've tried to repair VS2012 but nothing let me target .NET 4 and the Event log does not contain any related reports. Any suggestions or hints (besides going back to Win7/VS2010)?
I'm honestly not sure what's going on. I have VS 2012 Ultimate RTM and all versions of .NET are supported.
I'm almost positive I never installed any .NET frameworks manually, though I did install Visual Studio 2010 Express for Windows Phone from http://create.msdn.com.
.NET 4.5 is an in-place-upgrade and therefore replaces .NET 4.0. Consequently when I install .NET 4.5 with Visual Studio 2012 I can no longer develop applications for .NET 4.0.
As .NET 4.5 is not supported under Windows XP, how can I maintain my existing .NET 4.0 applications which still have to run under Windows XP after I installed Visual Studio 2012?
Until now I could always devlop .NET applications for every version, even .NET 1.1, as long as VS2003 was installed. I don't have a problem with Microsoft not supporting .NET 4.5 on XP, I think it's allright to cut off old stuff.
But as we have still customers using Windows XP, we need to be able to create .NET 4.0 programs at the same time as .NET 4.5.
EDIT:
I just had my first incompatibility issue: I installed VS 2012 on a Windows Server 2012. I created a project targeting .NET 4.0. In blend 4.0 I create a copy of a control template of a checkbox. The generated template contains references on colors which are available only under .NET 4.5. The solution cannot be compiled any longer. However the same case works fine on my Windows 7 installation.
I assume that the installation of .NET 4.5 has replaced the control templates for my standard controls. Therefore I cannot create copies any longer.
Ironically, it seems Mono supports much of the .NET 4.5 functionality, and that it can be installed on Windows XP.
If your need C# 5.0's async and your client refuses to upgrade it's OS, this can be an option.
I have run into some serious issues developing .NET programs for 4.0 against computers with 4.5 installed. One issue, for instance, is that if you are doing WPF development and have a private setter on a property - if you're binding to that property with Mode=TwoWay, you will not get an exception if you're developing against .NET 4.5! You should get an exception and you will if you're in an environment with only .NET 4.0 installed (even though you're developing to target 4.0 in Visual Studio). Now obviously you should not have Mode=TwoWay and a private setter, but maybe you had originally intended for the property to be only OneWay. The point is that this is just one of many examples of issues that are simply swept under the rug by 4.5 and has caused me to go back to developing in Windows 7 with Visual Studio 2010 and .NET 4.0 for anything targeting .NET 4.0.
In the meantime I have found a great blog of Scot Hanselman which answers my concerns: http://www.hanselman.com/blog/NETVersioningAndMultiTargetingNET45IsAnInplaceUpgradeToNET40.aspx
.NET 4.5 is an in-place-upgrade and replaces the .NET 4.0 CLR, but it will still be possible to create .NET 4.0 applications with Visual Studio 2012.
EDIT: I now installed the final release of VS2012. My existing .NET 4.0 projects compile and run, no problems so far. The only drawback is, it doesn't support Windows Installer Projects any longer. You can switch forward and backward between VS2010 and VS2012.
BIG EDIT: We should wait until Microsoft announces the final decision, it's not clear yet, only conclusions.
But, I think that Microsoft won't drop support for XP and Vista that easy, it appears that the matter of decreasing support is just for speed-purposes to show it to the developers.
Also, if the it comes true and Microsoft Stopped the support for XP and Vista, then you have the virtual machine as an excellent choice!
Best wishes
I found that links:
Microsoft .NET Framework 4 (Web Installer)
Microsoft .NET Framework 4 (Standalone Installer)
Microsoft .NET Framework 4 Client Profile (Standalone Installer)
Note that (2) the size is 48.0 MB and the (3) the size is 41.0 MB. It's not the REAL .Net 4 Full Standalone. :(
I want that installer in a usb pen drive because my app need of features of .Net 4 Full Framework (like MSBuild) and I will install in a enviroment without Internet access.
PS: I tested the (2) and really is the Client Profile with another name... :(
Actually, you already found the full .NET 4 SDK. Microsoft put in a lot of effort to decrease the size.
The Microsoft .NET Framework 4
redistributable package installs the
.NET Framework runtime and associated
files that are required to run and
develop applications to target the
.NET Framework 4.
Have a look at this hanselpost.
The prerequisites have changed since .NET 3.5 SP1, .NET 4.0 requires at least XP SP3, Windows 2003 SP2 or Vista SP1. .NET 3.5 could be installed on any version of these operating systems, including a 11 year old completely unpatched version of XP.
So the 3.5 installer also needs to be able to update a bunch of native Windows components.
Not having to include the Windows component updates and additions allowed for a significant size reduction. If that's an issue then you'll have to include the Windows service pack installers on your pen drive.