RE: some other problems
From: Michael Green (mikegreonline_at_microsoft.com)
Date: 03/01/04
- Next message: Michael Green: "RE: ISmartDocument in the SmartTags 2.0 library"
- Previous message: Michael Green: "RE: help:iframe problems"
- In reply to: Richard: "RE: some other problems"
- Next in thread: Richard: "RE: some other problems"
- Reply: Richard: "RE: some other problems"
- Reply: richard: "RE: some other problems"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 01 Mar 2004 19:35:10 GMT
Richard,
J# Browser controls are a replacement for Java Applets, not code-behind
projects. The J# redistributable implements the com.ms.wfc.html package and
with a few modifications to the HTML code your code should run without
modification. This is all explained in the J# documentation:
Visual J# Concepts
Upgrading Components That Use the com.ms.wfc.html Package
Visual J# fully supports the com.ms.wfc.html package. However, the
parameters of the <OBJECT> tag have been changed to enable classes to be
loaded from managed assemblies in a version-aware manner.
Therefore, when upgrading Visual J++ 6.0 components that use the
com.ms.wfc.html package, the HTML pages that contain the <OBJECT> tag need
to be appropriately modified.
The <OBJECT> tag used in Visual J++ 6.0 is as follows:
<OBJECT CLASSID="java:com.ms.wfc.html.DhModule" height=0 width=0 ...
VIEWASTEXT>
<PARAM NAME=__CODECLASS VALUE=UserClass>
<PARAM NAME=CABBASE VALUE=UserCabFile.CAB>
</OBJECT>
The <OBJECT> tag that must be used in Visual J# is as follows:
<OBJECT CLASSID="CLSID:CF83EA5E-0FFD-4476-9BF7-6C15F7F8BDCF" height=0
width=0 ... VIEWASTEXT>
<PARAM NAME=CODECLASS VALUE=UserAssembly#UserClass>
</OBJECT>
where:
CLASSID
Refers to the control used by Visual J# to host the user-defined class.
Developers should not change this value.
CODECLASS
Refers to the user-defined class (that extends DhDocument) and the managed
assembly that contains this class. The '#' token separates the assembly
name and the class name. The assembly name must be the name of the file and
must include the file extension. An attempt will be made to load the
assembly from the same location that the HTML page that access it is
located. It is also possible to specify a relative path for the assembly.
Note The user-defined class is always hosted on latest version of Visual
J# installed on the machine.
In this release of Visual J#, the VJSVERSION parameter tag is no longer
supported and will be ignored if included in an <OBJECT> tag.
For example, a typical <OBJECT> tag used in Visual J# might look as shown
below:
<OBJECT CLASSID="CLSID:CF83EA5E-0FFD-4476-9BF7-6C15F7F8BDCF" height=0
width=0 ... VIEWASTEXT>
<PARAM NAME=CODECLASS VALUE=MyAssembly.dll#MyUserClass>
</OBJECT>
Visual J# will load and run a component only if it is fully trusted by the
NET Framework security policy on the client computer. In order to be
considered fully trusted by the security policy on the client, one of the
following conditions must hold:
The component must have been signed with a keypair and the .NET Framework
security policy on the client computer modified to grant the FullTrust
named permission set to all components or applications signed with this
keypair. The component must have been signed with an Authenticode
certificate and the .NET Framework security policy on the client computer
modified to grant the FullTrust named permission set to all components or
applications signed with this certificate.
The .NET Framework security policy on the client computer has been modified
to grant the FullTrust named permission set to controls downloaded from the
Web site where the component is hosted. A component that is not considered
fully trusted by the client computer will not be allowed to run. When a
page containing such a component is loaded in Internet Explorer, an error
message is displayed in the status bar. Based on the Internet Explorer
security setting on the client, loading a page with such a component might
cause an ActiveX warning dialog box to be shown every time the page is
loaded. The user must click OK on the dialog to proceed with loading the
component.
>From looking at the fuslog you sent it appears there is a problem not
loading one of your dll's but rather one of the CLR's main dlls,
mscorlib.resources.dll. If you look in the log you will see a number of
lines that look like this:
Attempting download of new URL
file:///d:/samplecode1/Testaa/Testaa/Debug/zh-CN/mscorlib.resources.DLL.
All of these are trying to find this one dll and are failing. The assembly
in question is a resource assembly for simplified Chinese. Make sure you
have the localized version of the .Net Runtime installed for Simplified
Chinese.
I hope this is helpful,
Michael Green
Microsoft Developer Support
- Next message: Michael Green: "RE: ISmartDocument in the SmartTags 2.0 library"
- Previous message: Michael Green: "RE: help:iframe problems"
- In reply to: Richard: "RE: some other problems"
- Next in thread: Richard: "RE: some other problems"
- Reply: Richard: "RE: some other problems"
- Reply: richard: "RE: some other problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|