Even though I have set the OI10 printout to the classic mode set via OICONSOLE the TCL report uses the .net OIPI. This is not a problem but the first time I execute a TCL LIST command for the first time I get the following error in the status bar and NO report is displayed. Repeat the TCL LISt command the second time and all is OK.

This is on my development laptop NOT running the LH service.

"Base Exception: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions …"

Not sure if this is a bug or a setup issue.

Chris

Is it recommended I have the LH service running on my stand-alone laptop to get the full OI10 functionality. Just wondering if that is responsible for the TCL issue above.

The revparam file is ServerOnly = 0 in the OI10 root directory.

If I had to hazard a guess, did you specify the server when you ran client install on this laptop, rather than the local hard disk?

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Even though I have set the OI10 printout to the classic mode set via OICONSOLE the TCL report uses the .net OIPI. This is not a problem but the first time I execute a TCL LIST command for the first time I get the following error in the status bar and NO report is displayed. Repeat the TCL LISt command the second time and all is OK.

This is on my development laptop NOT running the LH service.

"Base Exception: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions …"

Not sure if this is a bug or a setup issue.

Chris

Hi, Chris.

Did you exit and re-enter OI after changing which OIPI you wanted to use? I believe the value is cached by default, so even if you changed it you won't see the change take effect until you next log in.

Also, please note that in 10.2.1 we've changed OIPI "classic" so that its window looks just like the OIPI.Net window - perhaps you ARE getting the OIPI classic output, but it doesn't look the same? On the right-hand top of the output window, there are 3 dots ("…") - if you press them, they should indicate if you're running Classic or .Net for sure.

Regarding the error you're seeing - that's implying that you're trying to run one of the .net assemblies over the network. Did you install OI on your dev laptop directly, or on a 'server' somewhere? If you installed it on a server, then did you run clientsetup.exe? When prompted for where you wanted to install the client files, did you specify a folder on your PC, or did you choose a location on the network? The clientsetup is designed to copy files from the OI installation folder to your local PC, specifically to avoid these kinds of errors - but sometimes people specify the "target" folder on some other system, which isn't the intent…

- Bryan Shumsky

Revelation Software, Inc.

Even though I have set the OI10 printout to the classic mode set via OICONSOLE the TCL report uses the .net OIPI. This is not a problem but the first time I execute a TCL LIST command for the first time I get the following error in the status bar and NO report is displayed. Repeat the TCL LISt command the second time and all is OK.

This is on my development laptop NOT running the LH service.

"Base Exception: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions …"

Not sure if this is a bug or a setup issue.

Chris

Hi, Chris.

Did you exit and re-enter OI after changing which OIPI you wanted to use? I believe the value is cached by default, so even if you changed it you won't see the change take effect until you next log in.

Also, please note that in 10.2.1 we've changed OIPI "classic" so that its window looks just like the OIPI.Net window - perhaps you ARE getting the OIPI classic output, but it doesn't look the same? On the right-hand top of the output window, there are 3 dots ("…") - if you press them, they should indicate if you're running Classic or .Net for sure.

Regarding the error you're seeing - that's implying that you're trying to run one of the .net assemblies over the network. Did you install OI on your dev laptop directly, or on a 'server' somewhere? If you installed it on a server, then did you run clientsetup.exe? When prompted for where you wanted to install the client files, did you specify a folder on your PC, or did you choose a location on the network? The clientsetup is designed to copy files from the OI installation folder to your local PC, specifically to avoid these kinds of errors - but sometimes people specify the "target" folder on some other system, which isn't the intent…

- Bryan Shumsky

Revelation Software, Inc.

I was able to tap and output the msg to a txt file.

here is the full msg:

Base Exception: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information

A bit more background is needed for you on this. This error is not occuring in the TCL from the IDE, it is a MD hook I created to show the return from a slect to show on the statusline of the mdi form that it is run from (Press F5)

This error was occuring on my PC and now it is not for some unknow reason, but, is for Chris.

The MD setup is:

<0> RTI_IDE_TCL

<1> P

<2>

<3>

<4>

<5> SYSOBJ

<6> HOOK_RTI_IDE_TCL



<0> RTI_IDE_TCL_ORIG

 

<1> P

<2>

<3>

<4>

<5> SYSOBJ

<6> RTI_IDE_TCL

HOOK_RTI_IDE_TCL is this:

subroutine HOOK_RTI_IDE_TCL(P1,P2,P3,P4,P5,P6)

declare function RTI_IDE_TCL_ORIG,Get_Property

declare subroutine Kazm_Win_Statusbar,set_property_only

$Insert App_Common_Ins



	StatusLineObject = Get_Property(MDI_Frame@, "STATUSLINE")



	RetVal = RTI_IDE_TCL_ORIG(P1,P2,P3)



	Result =get_property(StatusLineObject,"DEFPROP")

	Kazm_Win_Statusbar('setcaption', "", Result)

	set_property_only(StatusLineObject,"DEFPROP",'')



return ''

btw: regarding the OIPI output screen, I dont see the 3 dots. The report is produced by BRW (Not me, appears to be default) - is there an override for it not to use BRW as there actually is a bug I have reported

Take a look at issue 2739 where you can see a screenshot of the 'oipi' form.

Hi, Barry.

What's the KAZM_WIN_STATUSBAR? If your HOOK_RTI_IDE_TCL just returned after the call to RTI_IDE_TCL_ORIG, do you still get the error message?

Re: the BRW output. In the CFG_OIPI record, if field 8 is set to "1", that tells TCL to generate the output via BRW. If that's not what you want, change field 8 to "0" instead. Remember to exit and re-enter OI after you change the CFG_OIPI value, as it is normally cached.

- Bryan Shumsky

Revelation Software, Inc.

Hi, Barry.

What's the KAZM_WIN_STATUSBAR? If your HOOK_RTI_IDE_TCL just returned after the call to RTI_IDE_TCL_ORIG, do you still get the error message?

Re: the BRW output. In the CFG_OIPI record, if field 8 is set to "1", that tells TCL to generate the output via BRW. If that's not what you want, change field 8 to "0" instead. Remember to exit and re-enter OI after you change the CFG_OIPI value, as it is normally cached.

- Bryan Shumsky

Revelation Software, Inc.

Function to manage statusline updates

Yes (no display of course, but, no report.

CHANGED "Use XBand for TCL List statements" to "No"

ran the list statement again, no error (and correct formatting)

Error msg must be BRW related.

So, for the moment, happy with that as also the 'normal' rlist gives a nice progress msg.

View this thread on the Works forum...