Dyalog Forums

The first thing i´m going to do when trying out a new version is to run the samples.
Till now i still chose the <dyalog-folder>\Samples\asp.net as the basic application-folder because there is the web.config and the index.html.

Problem:
This time i became an error that the assembly tutorial.dll could not be found.

Solution:
The needed tutorial.dll is in the folder <dyalog-folder>\Samples\asp.net\tutorial\bin.
I copied the dll into the folder <dyalog-folder>\Samples\asp.net\bin and it was working.
Also the bridge130_unicode.dll is needed in this folder.


The next thing i will try is to debug an asp.net-application.
I read something about debugging gui-applications in one of the dyalog-helpfiles.
Hope this will work similar.

Regards,

Robert Beck

Debugging asp.net-applications works!

I have created a new web-project under visual studio 2010.
Into the bin-folder copied the following files:

bridge130_unicode.dll
dyalog130_unicode.dll
dyalognet.dll
dyalogprovider.dll
tutorial.dll

The files intro10.aspx and web.config I have added into the project. Right click on the project in visual studio and select "Add", and then "Add Existing Item...".
Then I have to set a breakpoint in the apl-code. To do this I chose the function "Render" and typed "+++" in line 3 of the code.
In the next step I recreated the tutorial.dll. It is important to uncheck "Runtime Application".

Now I started the tutorial.aspx from visual studio and the Dyalog-Debugger opened with a syntax error on the right line.

Today I want to separate the apl-code completly from the intro10.aspx.
I created a new class inherited from System.Web.UI.Page in an empty workspace.
Next I copied the Page_Load-event from the intro10.aspx to the new class.
Then added the following directive in the intro10.aspx:

<%@Page Language="Dyalog" Inherits="Intro10" src="Intro10.dws" %>

I don´t understand why, but it does not work. The dyalog-debugger comes up with an exception when i start the project.
Could not tell you the exactly Exception because I can´t reproduce it at the moment. It was something in the base-constructor (not my code).

Workaround:
Like in my second post explained, I have exported my workspace to a "Microsoft .Net Assembly" named Intro10X.dll.
In the intro10.aspx added this additional directive:

<%@Page Inherits="Intro10" CodeBehind="Intro10X"%>

Now it works fine. Also debugging works.

Hi Robert,

It sounds like you wish to do "Workspace Behind" in an ASP web page. Have you seen the "Workspace Behind" section in Chapter 8 of our .Net Interface Guide?

Could you send details of your exception, and your files to me at support@dyalog.com?

Regards,

Vince

Hi Vince,

thanks for your answer.
Meanwhile everything is working fine.

Regards
Robert