This question is locked. New answers and comments are not allowed.
When we move our files from the AppBuilder Windows Client to the AppBuilder VS Extension Project the project runs fine and the simulator works fine running our application as intended out of Visual Studio until the following scenario takes place:
When we run the project once again in the windows client (still using its original checked in code) the client still runs fine and our application still runs fine from the client but the Visual Studio project never runs again in the simulator from Visual Studio. Even the template project that comes with AppBuilder never runs again. It doesn't matter if I reboot the machine, uninstall the windows client, uninstall the VS extension and reinstall the VS extension. The template project that comes from AppBuilder for Visual Studio never runs again in the simulator. We get a 'Cannot call method hide of undefined' for the line of code in the template project app.js file for navigator.splashscreen.hide();
So to summarise the process again we have:
Telerik AppBuilder WIndows Client installed (latest version up to date) with a working appbuilder project running fine
and VS AppBuilder Extension installed in VS2013
Then we:
Create a new AppBuilder Project in VS2013
Copy the files across from our Windows Client Project from an export of that project (obviously not the proj file)
Run the project in VS2013 using the extension (all runs fine in the simulator)
NOW THE BREAKING PART
We once again run the old existing project that still runs fine in the Windows AppBuilder Client
That runs fine in the simulator from the Windows Client
Once again we run the project we now have in the VS2013 project from the VS Extension. It never runs again (reference errors etc., seems like bootstrapper never runs).
And as mentioned even creating a new blank VS2013 AppBuilder template project never runs again out of the box.
We have tried uninstalling everything, rebooting but all to no avail, the error seems to permanently persist now in that we cannot run anything again from VS2013 using the VS extension
We are not sure how to rectify this issue, that seems to have permanently screwed up being able to run any AppBuilder project from Visual Studio again
Matt
When we run the project once again in the windows client (still using its original checked in code) the client still runs fine and our application still runs fine from the client but the Visual Studio project never runs again in the simulator from Visual Studio. Even the template project that comes with AppBuilder never runs again. It doesn't matter if I reboot the machine, uninstall the windows client, uninstall the VS extension and reinstall the VS extension. The template project that comes from AppBuilder for Visual Studio never runs again in the simulator. We get a 'Cannot call method hide of undefined' for the line of code in the template project app.js file for navigator.splashscreen.hide();
So to summarise the process again we have:
Telerik AppBuilder WIndows Client installed (latest version up to date) with a working appbuilder project running fine
and VS AppBuilder Extension installed in VS2013
Then we:
Create a new AppBuilder Project in VS2013
Copy the files across from our Windows Client Project from an export of that project (obviously not the proj file)
Run the project in VS2013 using the extension (all runs fine in the simulator)
NOW THE BREAKING PART
We once again run the old existing project that still runs fine in the Windows AppBuilder Client
That runs fine in the simulator from the Windows Client
Once again we run the project we now have in the VS2013 project from the VS Extension. It never runs again (reference errors etc., seems like bootstrapper never runs).
And as mentioned even creating a new blank VS2013 AppBuilder template project never runs again out of the box.
We have tried uninstalling everything, rebooting but all to no avail, the error seems to permanently persist now in that we cannot run anything again from VS2013 using the VS extension
We are not sure how to rectify this issue, that seems to have permanently screwed up being able to run any AppBuilder project from Visual Studio again
Matt