I have a VB.NET 2008 (FW 3.5) app with J# 2.0 as a prerequisite.
For some problems I have to check during runtime if this framework is installed.
How can I do?
Thanks
Alessio
You may find the post "What registry keys indicate that J# is installed" helpful.
Related
I checked out http://msdn.microsoft.com/en-us/library/dd783499.aspx?cs-save-lang=1&cs-lang=vb#code-snippet-1. It should exist.
EDIT:
I tried it on vs2010 (different project, though), and it exists.
Enum.TryParse was added with .Net Framework 4.0.
You can easily tell this by looking at the Other Versions drop down menu in the documentation or the version Information:
.NET Framework
Supported in: 4.5, 4
.NET Framework Client Profile
Supported in: 4
Portable Class Library
Supported in: Portable Class Library
.NET for Windows Store apps
Supported in: Windows 8
So probably you're using an older .Net Framework version.
Do you have System Import?
Imports System
If you are in Visual Studio 2010, make sure you are targeting .NET Framework 4.0
I'm usually in WIX-land instead of InstallShield.
What's the equivalent of NETFRAMEWORK40FULL in InstallShield? Is there a better way to check for .NET 4.0 from InstallShield 2012?
Please note: I am not interested in installing it from the installer. Just a simple test to inform the user they need to install .NET 4.0 before continuing.
EDIT:
I could use a bootstrapper, but would rather not if there's a native InstallShield way of doing this.
I haven't done much on InstallShield. I hope this may address you query.
As stated in this question, thanks to some compilation trickery, Visual Studio 2010 allows a project targeting at .Net 3.5 to benefit from optional parameters.
Is it possible to achieve similar behavior with MonoDevelop 2.6b1?
EDIT:
This problem doesn't however affect xbuild which can successfully leverage dmcs (C#4.0 compiler) to target a 3.5 profile.
https://bugzilla.novell.com/show_bug.cgi?id=566247
Once it is marked as resolved, you know your request can be satisfied too.
While trying to install my application, when system tries to install .Net Framework, it gives an error.
Is there any source where I could download uninstalled .Net Framework 3.0 and provide my clients with application?
Thanks and best regards,
Furqan
Dot Net Framework 3.0 Redistributable
http://www.microsoft.com/downloads/details.aspx?FamilyID=10cc340b-f857-4a14-83f5-25634c3bf043&displaylang=en
Or the latest in 3.x (3.5 SP1)
http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en
Or the latest Redistributable
Dot Net Framework 4
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
I'm trying to deploy a VB.NET app which is an extension to Excel using VSTO. It works fine in the development environment, but when someone else (without a dev environment installed, just the .NET framework) installs it, they get:
The common language runtime could not be loaded by <application>. Contact your administrator for further assistance.
Google pops up the microsoft help page for this:
http://msdn.microsoft.com/en-us/library/6s0wczt9.aspx
But I've verified that the .NET versions are the same on both machines. For VSTO apps in 2k5 there was a specific vsto runtime library users needed to install -- is there something similar for VS2008 that I haven't found yet? Any ideas besides that?
Thanks in advance!
For VSTO apps built with Visual Studio 2008, The VSTO version 3.0 Runtime is required.
Here is the download page: http://www.microsoft.com/downloads/details.aspx?FamilyID=54eb3a5a-0e52-40f9-a2d1-eecd7a092dcb&DisplayLang=en
Make sure they have the correct version of the .NET framework. If they have .NET 1.1 (or even 2.0) installed, and you're targetting the 3.5 framework, you can get this error message.
We had the same problem. It's all to do with security policy.
There are issues with the security policy for your DLL's when running VSTO projects.
Namely you need to grant 'full trust' to your assemblies. What this means you have to A) sign your projects with a key, and B) register your assemblies as having full trust during deployment (which can be done easily with CASPOL.exe: http://msdn.microsoft.com/en-us/library/cb6t8dtz.aspx)
Its very easy to do. Alternatively you can roll your own security-setting assembly which you integrate into your msi (thats what we did)
Check out this MSDN Article for the full details:
http://msdn.microsoft.com/en-us/library/zdc263t0.aspx
Install VSTO runtime 3.0
Then update it to VSTO 3.0 SP1
also install VSTO_PTExtLibs.exe (PIA extension libs for runtime) if you are referencing these in your project.