Vs2008

broken image


  1. Vs2008 Redistributable
  2. Vs2008 C++ Version
  3. Vs2008 Sp1
  4. Vs2008 Runtime
  • I'm having difficulty with the 'add a variable' wizard on ARX projects that I created in VS2005 (or earlier) and migrated to VS2008. The migration was through the VS2008 wizard. When I right click on an edit box, combo box, etc. And want to add a variable (in my case control variables), after I've.
  • #vs2008 2.2K people have watched this. Watch short videos about #vs2008 on TikTok.
Home‎ > ‎Uploads‎ > ‎

Index of /archive/qt/4.8/4.8.5 Name Last modified Size Metadata: Parent Directory - qt-win-opensource-4.8.5-vs2010.exe. Screenshot of Visual Studio 2013, editing the source code of a C program. Windows 7 SP1 and later; Windows Server 2012 R2 and later. Project files to compile FFTW 3.2.2 with Visual Studio 2008 were sent to us by Nathaniel Meyer (nate at nutty dot ca): fftw-3.2.2-vs2008.zip. Project files to compile FFTW 3.1.2 with the Intel compilers under Visual Studio.NET 2003 were sent to us by Jin Tian (jintian at.

Unmanaged Exports

posted Jul 9, 2009, 9:23 AM by Robert Giesecke [ updated Dec 19, 2012, 12:23 PM]

Contents

  1. 1 How does it work?
  2. 2 Samples
  3. 3 Changes


How does it work?

Create a new classlibrary or proceed with an existing one.


Now you can write any kind of static method, decorate it with [DllExport] and use it from native code.
It works just like DllImport, so you can customize the marshalling of parameters/result with MarshalAsAttribute.
During compilation, my task will modify the IL to add the required exports.

Restrictions

  • What you cannot do is use overloaded exported methods inside the same class, even if you provide them with different export names.
  • Another restriction is that you cannot call an exported method recursively.
    • This seems to be a limitation of the runtime and I did not want to wrap your code in another, hidden method to make it work.

Samples

Basic sample

Showing how to provide an export alias (the name which will be seen from consuming processes) and calling convention. (Default is stdcall, the samples use Cdecl which is used by C/C++)

C#:

classTest
[DllExport('add', CallingConvention = CallingConvention.Cdecl)]
{
}

F#:

openSystem.Runtime.InteropServices
[<DllExport('add', CallingConvention = CallingConvention.Cdecl)>]
static memberTestExport(left : int,right : int) : int = left + right

VB.Net:

Imports RGiesecke.DllExport
PublicModuleTest
PublicFunction TestExport(left AsInt32, right AsInt32) AsInt32
EndFunction

Marshalling sample

You can also use the MarshalAsAttribute to control how the marshaller translates your .Net types into native types.
The example below shows how to mark a parameter to be returned to native code as an IUnknown-compatible interface reference.
btw, this is also how to pass objects between native and .Net ;-)
[Guid('Some GUID'),
InterfaceType(ComInterfaceType.InterfaceIsIUnknown)]
{
// without MarshalAs(UnmanagedType.BStr), .Net will marshal these strings as single-byte Ansi!
String Name
// this is how to add attributes to a getter's result parameter
get;
// this is how to add attributes to a setter's value parameter
set;

}
public classSample : ISample
publicString Name{ get; set; }
public int DoSomething(int value)
return value + 1;
}
static classExports
[DllExport]
public static void CreateSampleInstance([MarshalAs(UnmanagedType.Interface)]outISample instance)
instance = newSample{ Name = 'Test' };
}

Changes

  • Version 1.2.1

    • Deployed as nuget package!
      • Should install itself nicely over existing projects
    • no longer limited to C#!
      • pretty much any sane language that can create static methods with attributes should work
    • VS 2008 is no longer supported (it has no nuget support)
      • Also applies to Sharpdevelop 4.2, because my nuget scripts don't work in this version.
    • Various fixes regarding path reslution for ildasm.exe, ilasm.exe and lib.exe
      • it will no longer fail if it can't find lib.exe (it just won't produce .lib & .def files)
    • export names are escaped, so using il keywords like add won't be a problem any more
    • The task will only execute when you have selected a specific CPU target (x86, x64, Itanium) in your build options
      • Creating sub folders for each target was kinda creepy and VS' project references went crazy
    • Build events will now be fired after my task has finished (thx to Darin Higgins)
    • Uses a newer version of Mono.Cecil (0.9.5) to look for attributes
  • Version 1.1.3
    • In VS2008 and VS2010, the correct version of ILAsm/ILDasm will be used according to the TargetFramework. Only important for 2010 due to 4.0 / 2.0 runtime.
    • Temporary .def file will be removed as it isn't really required after having the .lib and .exp file.
    • Fixes to the .lib creation (export names had the real method name in the .lib, not the one that DllExport contained, while the DLL itself exported it correctly)
    • nicer Icon
    • TargetFramework is no longer set to 3.5 but left empty for the IDE to decide what makes sense (VS2005 obviously has no clue about this setting).
    • Autom. packaging of the C# project template and the archive on this page during build, to prevent uploading older versions.

  • Version 1.1.2

    • When provided with the location of lib.exe, it will create the .lib and .exp files that are required my MSVC
      • either autom. inside the VS IDE
      • having an environmental variable LibToolPath pointed to its directory
      • or adding a property LibToolPath to the project file
  • Version 1.1.1
  • I created a C# project template to make it very, very easy to setup the target and build task.
  • I also fixed some issues that could result in extreme slowdowns.
  • When you use the same export name for multiple methods, it will now create a warning which uses the pdb debug infos to point to the exact source locations.
License

Old Downloads removed...

The old downloads were removed, please use Nuget.
I went pretty far to make those install/uninstall scripts work nicely and undestructively, so please do use them :-)

Donation



  1. Setup
Vs2008

Note: Microsoft moved most of the Windows CE documentation to https://docs.microsoft.com/en-us/previous-versions/windows/embedded/gg154201(v=winembedded.80), and it is not indexed by Google.

This article describe the setup for application development on WinCE 5,6,7 with Visual Studio 2008. If you are interested in Windows Embedded Compact 2013 and Visual Studio 2012, 2013 or 2015 have a look here.

Setup

Install the following SW on your development PC.

Windows Mobile Device Center / ActiveSync

If you use Windows XP or an earlier version you need to install ActiveSync. Windows 7/8 will automatically use Windows Mobile Device Center when you connect your Toradex Module with the development PC

Visual Studio 2008

Download and install Visual Studio 2008. You may find more information in our Windows Embedded Compact Application Development article.

SDK

Install at least the SDK for WinCE 6.0 plus the SDK for the Win CE version you plan to develop for. To download and install SDK click here.

Remote Display tool

Vs2008 Redistributable

The Remote Display allows you to see the display content of the Toradex module even if it is not connected to a screen or the screen settings are invalid.

Vs2008

Development environment setup is complete.

Write your first Program

Vs2008

Note: Microsoft moved most of the Windows CE documentation to https://docs.microsoft.com/en-us/previous-versions/windows/embedded/gg154201(v=winembedded.80), and it is not indexed by Google.

This article describe the setup for application development on WinCE 5,6,7 with Visual Studio 2008. If you are interested in Windows Embedded Compact 2013 and Visual Studio 2012, 2013 or 2015 have a look here.

Setup

Install the following SW on your development PC.

Windows Mobile Device Center / ActiveSync

If you use Windows XP or an earlier version you need to install ActiveSync. Windows 7/8 will automatically use Windows Mobile Device Center when you connect your Toradex Module with the development PC

Visual Studio 2008

Download and install Visual Studio 2008. You may find more information in our Windows Embedded Compact Application Development article.

SDK

Install at least the SDK for WinCE 6.0 plus the SDK for the Win CE version you plan to develop for. To download and install SDK click here.

Remote Display tool

Vs2008 Redistributable

The Remote Display allows you to see the display content of the Toradex module even if it is not connected to a screen or the screen settings are invalid.

Development environment setup is complete.

Write your first Program

Get started with these projects:

Deployment and debugging in Visual Studio 2008

Before deploying and debugging the project to the Colibri module, connect the module via USB client port to the PC and power up the board. After a few seconds, the device will be shown as connected in Windows Mobile Device Center (for Windows 7/8) or Active Sync (for Windows XP).

Vs2008 C++ Version

Deployment and debugging in VS2008 can also be done over an Ethernet connection.

Vs2008 Sp1

NOTE:

Vs2008 Runtime

  • Use an enough strong power supply, we recommend 12V@2A
  • Use a USB 2.0 High Speed capable USB cable for reliable connection.
  • Debugging and deployment over an active sync connection works only if the explorer is enabled on the device (see Disable the Explorer).

See also





broken image
PreviousNext
Cookie Use
We use cookies to improve browsing experience, security, and data collection. By accepting, you agree to the use of cookies for advertising and analytics. You can change your cookie settings at any time. Learn More
Accept all
Settings
Decline All
Cookie Settings
Necessary Cookies
These cookies enable core functionality such as security, network management, and accessibility. These cookies can’t be switched off.
Analytics Cookies
These cookies help us better understand how visitors interact with our website and help us discover errors.
Preferences Cookies
These cookies allow the website to remember choices you've made to provide enhanced functionality and personalization.
Save