OpenNETCF & CE¨6 ??

andrés barré
Hello 
somebody already attempt to use OpenNETCF with CE6? I am trying to use it
but without positive results. at the same time when use CE5 works
perfectly, somebody already knows or had some experience with this DLL an
example of the code that does not work in CE6 and that if it works in CE5

using System;

using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using OpenNETCF;
using OpenNETCF.IO;

namespace gpio_cf1
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
        }

        private void Form1_Load(object sender, EventArgs e)
        {
        }

        private void textBox1_TextChanged(object sender, EventArgs e)
        {
        }

        private void button1_Click(object sender, EventArgs e)
        {
           OpenNETCF.IO.PhysicalAddressPointer pap = new
OpenNETCF.IO.PhysicalAddressPointer(0x56000000, 32);
            textBox1.Text = "" + (uint)pap.ReadInt32();
        }
    }
}

it is simple as soon as I am trying to read the value of an internal
registry.

this diagnosis for the case,!!!!

System.ArgumentNullException was unhandled
  Message="ArgumentNullException"
  StackTrace:
    at System.Runtime.InteropServices.Marshal.ReadInt32Internal()
    at System.Runtime.InteropServices.Marshal.ReadInt32()
    at OpenNETCF.IO.PhysicalAddressPointer.ReadInt32()
    at gpio_cf1.Form1.button1_Click()
    at System.Windows.Forms.Control.OnClick()
    at System.Windows.Forms.Button.OnClick()
    at System.Windows.Forms.ButtonBase.WnProc()
    at System.Windows.Forms.Control._InternalWnProc()
    at Microsoft.AGL.Forms.EVL.EnterMainLoop()
    at System.Windows.Forms.Application.Run()
    at gpio_cf1.Program.Main()
  InnerException: 

I repeat, in CE5.0 works perfectly. not thus in CE6.0

   some idea?

andrés barré
Windows CE 6.0 has a different security model and VirtualAlloc to a
physical address is no longer allowed.  Since this is what the
PhysicalAddressPointer class relies on to work, it causes the class to
fail.  The only workaround is to create an actual driver for the device
that exposes a method to do the memory-mapping for you.

 

 

------------------------

OpenNETCF Support Team

OpenNETCF Consulting

 

e: support@opennetcf.com

w: http://www.opennetcf.com/

------------------------