32 bit / 64 bit

[pfullarton]

Mike,

I understand that the WCL .NET Edition is designed for 32 bit architecture but wondered if it will run on the newer generation of 64 bit processors running Win 7?

Thanks,

Peter

[Mike Petrichenko]

Hello,

It not "will" it does. I can say more: all our development PCs run Win 7 Ultimate 64 bit.

[pfullarton]

Mike,

I little more on this inquiry.

I've built an app and it runs fine on my dev machine.  This is a standard 32bit  PC running Win7.  I'm getting 2 symptoms:

1)  App will not run on a 2nd machine after installation (if I remove WCL and rebuild - it runs fine - without BT functions, of course)
2)  Getting the 'wcl.dll' targets a different processor than the application'

Thx,

Peter

[pfullarton]

OK, so it should work.  The APP with WCL included just aborts immediately with the message '****** is NOT WORKING'.  Rebuilt without WCL included it runs fine - Any ideqs?

[pfullarton]

All I'm getting is an APP crash.  Here is the info from EVENT VIEWER.....

Log Name:      Application
Source:        Windows Error Reporting
Date:          15/08/2010 18:29:34
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      forum-PC
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: blue slate technology quest v1
P2: 1.0.0.0
P3: 4c6821fc
P4: Blue Slate Technology Quest V1
P5: 1.0.0.0
P6: 4c6821fc
P7: 3b
P8: e0
P9: System.InvalidOperationException
P10:

Attached files:
C:\Users\forum\AppData\Local\Temp\WERB316.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\forum\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_blue slate techn_c555f4c7aa6b751d354e85db1faf13a41ab7a95_1ef8b99b

Analysis symbol:
Rechecking for solution: 0
Report Id: aa421e16-a892-11df-aa77-00262d24369f
Report Status: 1
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-08-15T17:29:34.000000000Z" />
    <EventRecordID>4962</EventRecordID>
    <Channel>Application</Channel>
    <Computer>forum-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>CLR20r3</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>blue slate technology quest v1</Data>
    <Data>1.0.0.0</Data>
    <Data>4c6821fc</Data>
    <Data>Blue Slate Technology Quest V1</Data>
    <Data>1.0.0.0</Data>
    <Data>4c6821fc</Data>
    <Data>3b</Data>
    <Data>e0</Data>
    <Data>System.InvalidOperationException</Data>
    <Data>
    </Data>
    <Data>
C:\Users\forum\AppData\Local\Temp\WERB316.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\forum\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_blue slate techn_c555f4c7aa6b751d354e85db1faf13a41ab7a95_1ef8b99b</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>aa421e16-a892-11df-aa77-00262d24369f</Data>
    <Data>1</Data>
  </EventData>
</Event>

[Mike Petrichenko]

.NET error reports are absolutly useless and meaningless and informationless. So I can just guess that: http://forum.btframework.com/index.php/topic,957.0.html

[pfullarton]

Thanks Mike - It was the assembly setting as you suggested.  Problem now resolved.