|
ExecuteReader stored procedure execution type expects at least one resultset configuration
6/22/2010 11:26:33 AM
(Total replies: 0)
|
| Error:
"execute reader" stored procedure execution type expects at least one resultset configuration.
The Error also shows up during database validation.
Answer:
"Database Validation" looks at how you have configured the Processing Instructions against the database and determines if the configuration is ok.
From the description of the error, it seems that you haven't configured the stored procedures you want to generate code against.
For a quick start, look at the following ... |
|
|
|
OxyGen Code Generator 3.2 released!
6/9/2010 5:18:21 PM
(Total replies: 0)
|
| The primary goal of the 3.2 release is to support Visual Studio 2010.
1) Updates to the generated ASP.NET UI.
a) We change the paging parameters from Int64 to Int32. The change was made to deal with a long standing issue we had with the ASP.NET ObjectDataSource.
b) The generated ASP.NET FormView now uses datasource paging.
c) Appropriate values in the generated ASP.NET FormView now have links back to the relevant pages.
d) All links in the generated FormView controls now link to ... |
|
|
|
Method 'OxyData.Modelling.OutputManagement.OutputManager.GenerateStoredProcedures' not found
5/25/2010 10:23:47 AM
(Total replies: 0)
|
| It looks like build 3.2.1 picked up the wrong configuration.
If you are experiencing this issue, you will have to use "Virtual Stored Procedures" instead of "Stored Procedures" until a new build is released.
This is how to change your configuration to use "Virtual Stored Procedures",
1) Switch to "Projects" mode
2) In the vertical tabs select "Components"
3) In the "Database Access Mode", select "Virtual stored procedures"
This mean that your sql statements will be stored in a ... |
|
|
|
FAQ May 2010
5/7/2010 11:32:42 AM
(Total replies: 0)
|
| <b>1) How useful is OxyGen Code Generator (OCG) to a company that doesn't develop websites and uses SQL CE?</b>
OCG is made up of 36 individual generators, this isolation of generators allows our configuration system to setup the right set of generators for each task.
The generator operate at different levels and they all feed the same Entity Model, building up metadata as they execute.
What this means for you is that you can configure OCG to stop generation at the business layer (I like to ... |
|
|
|
The type initializer for 'OxyData.Diagnostics.ComputerSystem' threw an exception
5/6/2010 2:17:43 PM
(Total replies: 1)
|
| An error has been encountered while generating the source code. The type initializer for 'OxyData.Diagnostics.ComputerSystem' threw an exception.
An error has been encountered while generating the source code. The type initializer for 'OxyData.Diagnostics.ComputerSystem' threw an exception. The type initializer for 'OxyData.Diagnostics.ComputerSystem' threw an exception. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ... |
|
|
|
Re: The type initializer for 'OxyData.Diagnostics.ComputerSystem' threw an exception
5/6/2010 2:18:43 PM
(Total replies: 0)
|
| It seems that the "Windows Management Instrumentation" Service is not running on your computer.
In case you are a technical person, the following code seems to be the problem:
System.Management.SelectQuery query = new System.Management.SelectQuery("Win32_ComputerSystem");
System.Management.ManagementObjectSearcher searcher = new System.Management.ManagementObjectSearcher(query);
foreach (ManagementObject mo in searcher.Get())
{
val.DomainName = ... |
|
|
|
|
|
|
|
|
|
|
|
|
Re: Configuration cannot be changed after code generation
3/2/2010 10:33:56 AM
(Total replies: 0)
|
| Josephlau,
Thanks for the suggestions, but am not clear on one of them:
"I also suggest there is value field for Select table process instruction, that generate additional methods"
I am not quite sure what you mean by that. |
|