Actually, I have reproduced the problem.
Looks like you use Ignition.StartFromApplicationConfiguration() method.
Instead,
try Ignition.StartFromApplicationConfiguration("igniteConfiguration")
overload.
On Fri, Mar 31, 2017 at 6:15 PM, Pavel Tupitsyn <[email protected]>
wrote:
> Hi,
>
> Yes, you certainly can use Ignite in ASP.NET project.
>
> There are a couple of things to be tweaked:
> 1) IgniteHome: https://apacheignite-net.readme.io/docs/deployment#
> section-aspnet-deployment
> 2) Stop on DomainUnload and use unique GridName: https://
> apacheignite-net.readme.io/docs/deployment#section-iis-
> application-pool-lifecycle-appdomains-and-ignitenet
>
> As for the error you get, can you attach full stack trace?
>
> Pavel
>
> On Fri, Mar 31, 2017 at 6:06 PM, ozgurnevres <[email protected]>
> wrote:
>
>> Hi,
>> I want to use Ignite within my asp.net mvc project but I don't want it
>> use
>> as a Output Cache Provider or Session State Store Provider. I want to use
>> it
>> as a database, and run sql queries on it, i.e. querying products. Is this
>> possible?
>>
>> When I try to start Ignite in Application_Start in Global.asax, it throws
>> "exePath must be specified when not running inside a stand alone exe"
>> exception.
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Can-I-use-Ignite-as-a-database-within-my-
>> asp-net-mvc-project-not-as-Output-Cache-Provider-or-Session-tp11624.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
