MvvM Light Toolkit Certificate Error - mvvm-light

I recently installed the MvvM Light Toolkit and created the default Windows 8.1 XAML Application Project Template.
When I compile it I get the following warnings:
"Warning 6 Certificate file 'MvvmLight.Win8_TemporaryKey.pfx' not found. MvvmLight1"
"Warning 7 The certificate specified is not valid for signing. For more information about valid certificates, see http://go.microsoft.com/fwlink/?LinkID=241478. MvvmLight1"
I am unable to build an application package with these errors present and I am unable to side-load the project to test it on other boxes.
If I create a default Windows 8.1 XAML not using the MvvM Light template, it works and compiles fine. I can build an application package with no issues and side-load the app correctly.
What am I missing?

Renew the certificate:
In Solution Explorer, open the shortcut menu for the .appxmanifest file, choose Open With, and then choose App Manifest Designer.
In the App Manifest Designer, choose the Packaging tab, and then choose the Choose Certificate button.
In the Choose Certificate dialog box, expand the Configure Certificate list, and then choose Create test certificate.
In the Create test certificate dialog box, click the OK button.

Related

Window Installer custom action fails for non-Admins

I have a windows setup project along with my project(WPF application) where I am adding a 3rd party USB driver(Silicon Labs USBXpressInstaller.exe) as a Custom Action in the setup project which makes my .MSI file along with the USB driver.
Project Tree: MyProject and SetUp Project
Custom Action for my SetUp Project:
After I build the project and the setup project, it is installing fine if the user is an Admin but gives the error pop-up "There is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor"(see below image) every time non-Admin tries to install the MSI. How can I fix this issue?
Any help would be really appreciated. Thank you in advance.
Thanks,
Sudheer
Edits: Below are the properties of my Setup project
Below are the properties of the Custom Action
Edits (08/06/2021): How can I suppress the below window when a non-admin is installing the msi?
Latest Update: I received a call from a client saying that they are not able to install the application at all. The user has DOMAIN ADMINISTRATOR rights for the PC he is trying to install on. For me, it is working now once I enter the Admin password (which I want to suppress). But, for the DOMAIN ADMINISTRATOR, there is no UAC pop-up shown as they are in the ADMINISTRATOR group but does not install as well.

Microsoft Project unable to establish a connection with Project Server 2016

I just built a Project Server 2016 and have connection troubles. Since this is a proof of concept, I did not use TLS. The URL is just http://xxxxxxxxxxxxx/sites/PWA I'm using the Project Permissions Mode.
I am testing with an unactivated copy of Project Professional 2013
I set the version in PWA Settings
My client computer is not in the same domain as my Project Server. I choose the domain\user name when starting MS Project:
Project does not prompt for a password. It immediately gives an error:
So next time, I choose work offline. Project opens and I check the Info page:
I click Connect to Server and it does. Still no password prompt.
However, I cannot open a project from the Project Server.
Meanwhile, I have no problems on PWA making, editing, saving, publishing, checking in, etc. I made a new project and set the permissions correctly.
When I try to open it in Project by clicking the icon on the web page,
I get the same error.
What am I missing?
I hate it when I discover my own dumb mistake an hour after posting a question.
Apparently, you must only use alphanumeric characters when you Add a Project Web Account in MS Project.
In the Info -> Manage Accounts -> Project Web Accounts dialog box, I deleted my Project Web accounts except "Computer"
I closed and restarted MS Project Professional
In the Info -> Manage Accounts -> Project Web Accounts dialog box, I added a new account but I only used letters in the Name field
I closed and restarted MS Project Professional
Logged into the new Project Web Account
Everything works now.
Apologies for wasting your time. Thanks for looking.

Newly created Asp.net Web App can ONLY RUN ONCE (in VS2017)

Intro:
When i run an asp.net web app that is freshly created, it runs just fine.
However, it runs only for the 1st time. Subsequent runs will fail with this message:
The only way to make it run again is to restart VS2017.
Not even restarting IIS/IISExpress will make it work again.
At this point my instincts tell me there is something stupid/silly going on. What on earth is going on here?
Here is my configuration:
I am using Visual Studio 2017 Version 15.8.4
.Net Framework Version 4.7.03056
Project: Asp.net Web Application (.Net Framework) ==> MVC
This is being run under - IIS Express (Internet Explorer)
Here are more details about the error im seeing:
The error page simply says "Can't reach this page".
When i click on the "More information" expansion link, i see following (mentioned above):
There was a temporary DNS error. Try refreshing the page.
Error Code: INET_E_RESOURCE_NOT_FOUND
Now, if i click on the "Fix connection problems" button, the Windows Network Diagnostics window popups up and says:
The remove device or resource won't accept this connection
If i click on "View detailed information" link at the bottom of this popup, i see following details:
The device or resource (localhost) is not set up to accept connections on port 'X' (where X is my localhost dev port).
Summary:
In the end, there is no real reason why port 'X' is not working any more. If i change the port number from Visual Studio the web app will run. But as i mentioned before, restarting Visual Studio will allow me to run for the 1st time.
* Updated *
I found a great work-around solution. Instead of running (F5), i
simply choose a view (.CSHTML) and execute that view itself
(right-click --> View in browser). This seems to work just fine every
time without messing up the port.

Host NetBean html5 app on iis

I download NetBean IDE and did the Getting Started Tutorial
but now I want to host the site on my local IIS and I can't find in Google way of doing it.
Someone know if it possible? and if yes how?
Note: I am coming from the world of ASP.NET and I used to host my web apps on IIS...
If you open Project Properties dialog (right click on the project and select Project Properties) and switch to Run category, there is a field called Web Server. NetBeans uses for HTML5 projects Embedded server by default but if you place your project to some "DocumentRoot" (sorry, don't know the terminology of IIS), then you can switch to External server in the the dialog and provide URL at which your project is available.
Note that NetBeans won't control your IIS, you simply provides URL which should be opened in browser once you run the project (so the server must be already running and your project must be in the document root)

Publishing an ASP.Net web application to a mapped drive with Visual Studio 2008 and Windows 7

We have a shared drive where web applications are published to. When I attempt to publish I get the following error:
------ Publish started: Project: XXX.Web, Configuration: Release Any CPU ------
Connecting to T:\WebSites\XXX\...
Unable to create the Web site 'T:\WebSites\XXX'. The path 'T:\WebSites\XXX' does not exist or you do not have access. The system cannot find the path specified.
Details
OS: Windows 7
IDE: Visual Studio 2008 (running as administrator)
Path exists? Yup.
I assume it's some permissions issue, but I have no idea where to start.
If anyone is still wondering, I had this same problem in Visual Studio 2012 with MVC4 in windows 7. I had previously published to a mapped drive and now all of a sudden it would no longer publish. In windows explorer I could see the mapped drive, but visual studio claimed it could not find the drive.
It turns out that if you are running visual studio in admin mode and your drive wasn't mapped in admin mode, you have to remap it.
(solution)
To do this, run explorer in admin mode, and then re-map your drive. Afterwards visual studio should be able to see the drive again.
I had this same problem with VS2010 and what worked for me is to click the [...] button next to the target location and rebrowse to the destination folder. Could be that VS is showing one path in the publish and output window, but really trying to access some other folder that's protected in Win7. That's why it worked in XP and not Win7 because Win7 has many more secure folders.
There are two points of check.
Share permissions.
File permissions.
You can both found on the remote computer, right click on the folder name -> permissions, and you see the Sharing and the Security tab. Change them, to left you write.
Help: how to share files:
http://www.howtogeek.com/howto/windows-7/share-files-and-printers-in-windows-7-with-homegroup/
and a video tutorial about :
http://www.youtube.com/watch?v=BWB9pu1T2dQ
Video tutorial for share folder base on my answer
http://www.youtube.com/watch?v=OomgNBAv0hI&feature=related
When you say administrator I will assume that you are an administrator to both the computer and the server containing the mapped drive. If that is the case then,
You might want to give this a shot:
To resolve this problem, add a MIME type for the .tmp file in IIS. To do so, follow these steps:
In Control Panel, open Administrative Tools, and then double-click Internet Information Services.
Expand the (local computer) node, and then expand Web Sites.
Right-click Default Web Site, and then click Properties.
In Default Web Site Properties, click the HTTP Headers Tab.
Click MIME Types. In MIME Types, click New to register a file extension.
In the Extension textbox, type .tmp . In the MIME Type textbox, type temp.
Click OK.
http://support.microsoft.com/kb/817264
If you are not in "Admin" mode and you are still having the issue, you can copy the "Target Location" path setting in your publish profile in VS, and then go to the file menu and check if you have access to that location, if you are prompted to enter user credentials, enter your credentials, this will allow Visual Studio to have the credentials needed. Now, go back to the publish profile and retry, it will use the credentials you just entered.

Resources