FAQs

The Express edition is free. The Professional Plus edition is for sale.

Yes. You need to register/activate AspCoreGen 3.0 Razor Professional Plus before use. You will need an internet connection to activate it. Registration and activation is done through the software interface. You don't need to activate the Express Edition.

No. You just need internet connection when you first activate the product and everytime you want to check for updates.

No catch at all. You can download it for free. You can give copies to your friends. You don't have to register. There's no trial date end (because it's not a trial). There are no pop-ups reminding you to buy the Professional Plus Edition. No Activation required. Absolutely no catch. Oh yeah, you cannot profit from it by selling or distributing it, etc.

Professional Plus is for sale, Express is free. Express generates just one type of Razor Page; the Unbound View. Unbound views are views not bound to the database. The Data-Tier/Data Layer does not have code that connects to the database, you will need to manually add these code yourself. For a more complete list of the differences, please see the Product Edition Comparison found on the side menu. And of course the price.

No it's not a component. It is a tool/application (.exe) that generates Razor Pages/classes based on your MS SQL Server 2000 and later database or an attached SQL Express.

You need an MS SQL 2000 or later database or an attached SQL Express, or SQL Express, and the .NET Framework Core 3.1 installed in your pc.

With Visual Studio 2019, yes. It's specifically made for the .NET Core 3.1 Framework. With older Visual Studio editions, no, because it will not compile .NET Core 3.1 classes. You can also use other IDEs if you like, the generated Razor Pages/classes are not tied to a specific IDE.

AspCoreGen 3.0 Razor is created using .NET Framework Core 3.1.

AspCoreGen 3.0 Razor is super easy to use. As a matter of fact, there's just One main interface, and One main button to click. AspCoreGen 3.0 Razor was created for C# programmers, therefore you need to know C#. There's also the understanding that you already know MS SQL 2000 or later since you need a database for AspCoreGen 3.0 Razor to look at to be able to generate the code.

Yes. You have two (3) options; Linq-to-Entities (Entity Framework Core), Classic ADO.NET using Ad-Hoc/Dynamic SQL, or Classic ADO.NET using Stored Procedures.

No. AspCoreGen 3.0 Razor only supports Microsoft SQL 2000 or later.

Yes. You need to attach your SQL Express database to an MS SQL 2000 or later database to do this. Or you can use Microsoft SQL Server Express.

Yes if the generated code's path is the same as your current project's path/directory. Note: Some files like the Business Object classes and the Data Layer classes are only generated once, they are not overwritten. Make sure to use a path/directory other than your project path/directory, then just copy the code you need into your project/website. E.g. if your website path is: C:\Inetpub\wwwroot\YourApp, then choose a different path for your generated code, e.g. use C:\GeneratedCode instead.

This means that you don't have access to the path/directory where you are trying to put the generated code. Make sure to choose a path/directory you have write access to.

You need admin rights on this Microsoft SQL 2000 or later database. If you already have admin rights to the database, then make sure that your username and password are correct. A blank password will not work.

No. Please download AspCoreGen 3.0 Razor Express, this is our free product.

No. We have 2 editions, Express which is Free and the Professional Plus which is for sale. Please download AspCoreGen 3.0 Razor Express, this is our free product. We also have sample generated projects which can be downloaded in the Demos & Examples page, in the bottom of the page.

This is to remind you (and the only warning) that you're using a very powerful product. All of our products will overwrite your files without warning. It will also overwrite stored procedures on your database. We suggest you use it in a development environment against a local database.

Yes.

Yes.

Yes.

C#.

You can generate code for .NET Framework Core 3.1

Yes. You can install both the Professional Plus and Express edition in the same computer.

Yes.

Yes. Bottom line: You can use the generated code with any client that uses C# (.NET Framework Core 3.1).

Yes. Add your code or override a function/method in the BusinessObject and DataLayer parent classes. These classes are only generated once and are not overwritten.

No. Although technically you can, we strongly suggest that you do not. All generated stored procedures will be overwritten every time you generate code. Instead, add your own stored procedure, then add the respective middle-tier code in the BusinessObject class and the data-tier code in the DataLayer class. *You can use the BusinessObjectBase and DataLayerBase classes as guide.

All our products are delivered digitally via download.

Updates yes. Upgrades no. Yes you are entitled to product updates and patches whenever they're released. We don't have upgrade pricing to any of our products.

You can install 1 developer license of AspCoreGen Professional Plus up to 2 computers or 2 virtual machines. You can install the free Express Edition to as many computers as you like. A developer license can be used by 1 developer, and cannot be shared with others. You cannot reuse the same license every time you buy or get a new (or used) computer, or create a virtual machine.

1 developer license can only be used by 1 developer. You will need to purchase 1 license of the Professional Plus Edition for each of the developer who's going to use this product.

No. Although students/teachers can learn from the generated code, AspCoreGen Professional Plus is meant for professional programmers. But please feel free to download our free product, AspCoreGen Express.

Yes. We may give discounts when you buy more than one (quantity) product. Please contact our sales team at to discuss your purchasing needs.

AspCoreGen only works for a Microsoft SQL Server database. You can use it to generated code for as many databases as you like. However, you can only generate code for 1 database at a time.

Yes. It doesn't just generate scaffolding for the controllers, it also generates code in each IActionResult method whether to fill a grid, retrieve data, insert data, delete an item, retrieve a collection based on id, etc. It also generates the related models, views, view models, entity framework linq-to-entity classes, business and data tier, stored procedures or ad-hoc SQL, and the optional web API service, and more. AspCoreGen has a very powerful code generation engine which can spit a million lines of generated code combined in as little as a minute.

AspCoreGen 3.0 Razor Professional Plus can only be downloaded once. Once you download it, make sure to keep it in a safe place. Our Express line of products may be downloaded as many times as you like.

Yes, please see the notes page. At first use you will need to fill a few required fields to start generating code such as:

- Server (database, it defaults to localhost)
- Name (database)
- User Name (database)
- Password (database)
- Check whether you want Linq-to-Entities, Stored Procedures, or Ad-Hoc SQL
- Web Application Name you want generated
- Directory where you want the Web Application to be generated in
- Business Layer and Data Layer Project Name
- Check whether you want to use a Web API, then enter the Web API Project Name
- Check the (type of) Razor Pages you want generated (by default they are all checked)

Once these are filled, the next time you generate code from the same database, all you really have to do is click the "Generate Code..." button. This is very useful because as developers, we would add new tables, or even new fields to an existing table in our database, and these additions and updates can go on forever while we're developing code for the same application. Being able to click just One button to generate code over and over again is very convenient and does not take away our focus on the current application we're developing for.

This same principle also applies when generating code for Database Views.