John Browne

Mobilize.Net Staff
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About John Browne

  • Rank
    Staff
  1. It looks like the problem might be related to the existing installation of VS2010. The installer looks for a file called VSIXInstaller.exe which is also on your VS2010 instance; but the SL Bridge doesn't support 2010 so there's a built in conflict. Suggestion is to rename C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\VSIXInstaller.exe to vsixinstaller.bak, then re-run the SL Bridge setup program. After it's completed, you can rename the VS2010 file back to .exe. Note: we're not sure this will work, but it's easier than uninstalling VS2010.
  2. Sorry for the delay, this is a bit puzzling. We think it might be related to the version(s) of Visual Studio installed on the dev machine. Can you check and tell us please which versions of Visual Studio are installed?
  3. Hi @wangw, you inspired me to write a blog post about this problem and how to fix it. You can read it here: https://www.mobilize.net/blog/vb6-to-.net-missing-a-reference
  4. Hi Zimo85, Can you provide a little more information? Did you have the Silverlight Bridge previously installed? If so, did you uninstall it before running this setup using the Control Panel or did you uninstall it from inside Visual Studio?
  5. This has cropped up before: it's a VS problem. See and also here: https://connect.microsoft.com/VisualStudio/feedback/details/2891723/microsoft-appxpackage-targets-causes-build-failures for a workaround.
  6. Hello Jack, Are you sure this is a conforming and complete Windows Phone Silverlight project (version 8.0 or 8.1)? If so, and you don't see the migration option, try uninstalling the extension and reinstalling it as an admin.
  7. Yes, VBUC fully supports Windows 10 and all prior versions back to XP.
  8. Let's start a thread here documenting the things that will have to be done after migrating a C# app to HTML with WebMAP. I'd like to see both issues identified as well as solutions and even code if possible. I'll start: Printing: Suppose your Windows app performs a printing task, perhaps an invoice to be mailed or a shipping label.You might have used Microsoft Word as a formatting tool before you sent your file to the printer as well. In your browser, you won't have access either to a printer or to Word for formatting. Solution: Create a PDF. Here's a web service from Adobe that will create a PDF from XML data. Then you can pass a link to the PDF to the browser for downloading to the local machine for offline printing. If you don't want to use LiveCycle from Adobe, here's an article describing taking an HTML view and creating a PDF from it.
  9. Here are two blog posts (so far) that drill down on our app architecture: http://www.mobilize.net/blog/webmap-app-architecture-part-1 http://www.mobilize.net/blog/webmap-app-architecture-part-2
  10. Great question. There's a short answer, and a longer one. The short answer is: on the server side, we create an ASP.NET MVC single page application. We also use Unity framework from Microsoft for inversion of control (aka dependency injection) as part of our state management approach. We also use some JavaScript frameworks, such as KendoUI from Telerik, or AngularJS (with Bootstrap). On the client side we use HTML5 and CSS with either Kendo or Angular for MVVM. Our Angular target (you have to choose when migrating an app between targeting Kendo for a more Windows-like UX or Angular for a more Web-like UX) includes Bootstrap for responsive design. For the longer answer check the blog--I have one article that introduces our architecture and will be creating more soon.
  11. The good news is if you have VB6 you can take that app all the way to the Web. This in itself is pretty amazing, kind of like taking a Fokker tri-plane from WWI and turning it into a space ship.Here's the basic idea: Use VBUC to migrate your VB6 code to .NET with C# as the output language. Get the resulting C# app to compile with no errors. Warnings are ok and you don't have to worry at this point about runtime issues.Sign up on studio.mobilize.net for a free account and create a new WebMAP3 migration.Point the assessment tool at your new C# application.Run the assessment and check the results. Queue the migration for either Kendo or Angular targets.Get the output. Now you can focus on fixing runtime issues and those things from your original VB6 desktop app that don't have a corollary in a Web app.
  12. Be sure to read this about configuring Visual Studio to compile WebMAP code correctly.