I was hesitant about experimenting with Lightswitch, but once I did it really was so simple, easy-to-use, and powerful that I fell in love. It was taking me only a few hours to put together some really meaningful software that I was enjoying working with, as well as developing. Lightswitch helped me put together software and debug it so it worked amazingly well...in debugging mode.But as soon as I try to publish on my own system, or deploy the published solution to another system the software just won't work. The error messages are confusing (if they tell you anything at all) and the solutions are even more tedious and time-consuming.If the goal of Lightswitch (which the descriptions when I downloaded it told me it is) was to make the development and deployment of the software easier on the developer it is missing the mark. I can develop amazingly fast. I love that part! But then I can't use the software unless I open it up in Visual Studio and run it in debugging mode.I've followed the convoluted instructions on making certain that SQL Express is installed on my dev system and on the system I tried to deploy to. I made certain to use Web Platform Installer and that the Visual Studio Lightswitch and Local Host software was installed on both system. I've published numerous versions of the software trying multiple types of settings. Half the time the publishing has an error for seemingly no reason. The other half everything seems fine but all I see are my screens taking forever to load and then popping up an error message that gives no decent instruction on how to fix the problems to get it working.I also don't understand why when I publish and then deploy a solution to a system as a Tier-2 desktop app run locally that the install process and verification is run EVERY time you supposedly have already installed the solution. The links created to the software on the start menu continue to install the application and add another entry into the Control Panel's Remove Program listings. And sometimes they have different description information such as "localhost" on one and not on another. And the proper logo/icon displayed on one, but just the standard Lightswitch/Silverlight/blank software logo on another.If I could actually create the software, make certain the system I'm deploying it to has necessary requirements, then install it on the deploy-system and use it...I would be in heaven.But right now there isn't even instructions telling how many files and what data needs to be transfered along with the supposedly "One Click" install that continues to not create a working solution on my dev system or my deploy system.Can I see testing this out on some monthly-fee server hosting package with so much more complicated installation requirements when I can't even get a local published solution to run outside of debugging? I don't think so. Please fix deployment. It shouldn't take days to get a system running the software when it works perfectly in debugging.
Please wait...