Iron Speed Technical Forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
ADW

Registered:
Posts: 106
Reply with quote  #1 
I've just tried ISD 10 for the first time and I'm getting some compilation errors.

The setup is:
 - A clean ISD 10.0.0.13834 installation on a Windows XP SP3 VM.
 - A MS SQL Database (GSS10)
 - A new application built with the Pinot Grigio theme.
 - Application Settings are:
    - Application Type: Web application for .NET
    - Code Language: Visual Basic .NET
    - .NET Framework: 4.0 (Visual Studio 2010)
    - SQL Statement Generation: Stored Procedures.

The application builds ok, but when I try to run it I get the compilation errors. (see attached image)

ADW

Attached Images
Click image for larger version - Name: Compilation-Errors.png, Views: 56, Size: 41.73 KB 

ADW

Registered:
Posts: 106
Reply with quote  #2 
Ok, I've done some more testing with ISD 10 and this problem only occurs if I include a SQL View in the build.  With the SQL View included, I get the normal Stored Procedures error, but it seems that ISD 10 then fails to build some other bits of the application.  If I then do a Build / Rebuild All from the menu, the application builds successfully and I can run it in the local browser, however a lot of the SQL Stored Procedures are missing.  They are showing up in the Stored Procedures section of the databases tab in ISD, but they are not being applied correctly to the SQL database.

ADW
Kirill

Avatar / Picture

Registered:
Posts: 223
Reply with quote  #3 
To apply Stored Procedures to a server you need to click Regenerate Stored Procedures.
Rebuild will not install or override SP in the server
ADW

Registered:
Posts: 106
Reply with quote  #4 
I've successfully migrated my current application to 10.0.1, and so far it seems much better than 10.0.0.

However, a couple of problems that I've mentioned before still exist.

1. If ISD encounters an error applying the stored procedures to a SQL database, it stops and doesn't try to apply any more procedures after the one that caused the error.  In my case, the error occurs when applying the stored procedures for a SQL View called Scorecard.  Therefore because the procedures are applied in alphabetical order, anything after Scorexxxxx doesn't get done.

2. If a SQL view is included in an application build, ISD generates a lot more pages that it should.  For example, I've just done a new application based on an SQL database with 11 tables and one view, where I asked ISD to generate 11 pages for each table.  If I include the view in the build, it generates 23 pages for each table and the view.  If I don't include the view, it generates the correct number of pages for each table.

On a new application, both these problems can be worked around by building the app in two passes, first the tables & then the views, if any. That way all the stored procedures and pages for the tables get generated correctly, and the ones for the SQL views can be added on the second pass.

I think the ISD developers really need to look at how ISD handles SQL views. There is a lot of extra work required when views are included in an application build, and TBH any complex application would require at least a couple of pages where data is pulled from two or more joined tables.  At the very least, a decent tutorial or white paper on how to properly build pages from views and how to get around ISD's shortcomings in this area would be a big help.

ADW
Kirill

Avatar / Picture

Registered:
Posts: 223
Reply with quote  #5 
On issue #1: Yes, this is the Design and it always has been. We believe, that if it is impossible to create Stored Procedure there is really no reason to create others. Because if we just skip one failed procedure and create others on the runtime this failed procedure will reveal itself at the most embarrassing moment to end-users. So since way back we always had this logic.

On issue #2 - I can't confirm that because we never have seen such behavior. When I include View we generate exactly same pages as when I do not. If you see otherwise I suggest to open support case, upload your schema and application and we will have a look on your specific situation.
JimiJ

Avatar / Picture

MVP Developer
Registered:
Posts: 1,966
Reply with quote  #6 
Neither I can reproduce Issue # 2 using both 4 & 4.5 Net Frameworks against MS SQL 2008 R2. 
The behavior I am getting always follows as what describes by Kirill.
 

Jimi J

__________________

  Jaime Jegonia
[jts_logo]

Iron Speed MVP Developer
 

". . . and whoever sows generously will also reap generously" 2 Cor 9:6

sdms

Registered:
Posts: 139
Reply with quote  #7 
I struck the same issue about a month ago and included this issue in a support ticket but I was unable to reproduce it and same for support. In my case it was v10.0.0, SQL Server 2008 and I was including views. After the wizard had finished I had three of everything (tables and views) e.g. AddUser, AddUser1, AddUser2

It hasn't happened since but keeping an eye out if it happens again

Steve
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Download Iron Speed Designer

Terms of Service Privacy Statement