Meteor file on new created project is missing - meteor

I used meteor for the first time yesterday and i was doing well. Today i try to create an new project to follow some tutorials and it was impossible i was receiving this message.
'meteor' is not recognized as an internal or external command, operable program or batch file.
but when i try to create a project on C:\users\any\AppData\Local.meteor the project is successfully created, so i go inside the folder of my new project using cd newproject and then type meteor and now the meteor should start building application but nothing happening, i again receive the same message
'meteor' is not recognized as an internal or external command, operable program or batch file.
someone who can help?

You may fix this issue by adding %USERPROFILE%\AppData\Local\.meteor; to your PATH environment variable.

Related

Understand backend in QtService

I wrote a daemon using Skycoder42/QtService.
It works when run from QtCteator but on the server, I get the below error
qtservice: No backend found for the name "standard"
In the project document, I can't find anything
what is the backend? How can I install the service and start it?
Finally, I find the solution:
We must copy the path/to/qt/gcc_64/plugins/servicebackends directory next to executable

Converted UWP... Nothing Happens

I have converted a Win32 Application to UWP using MakeAppX and it doesn't seem to run. When I click the icon in the start menu literally nothing happens except a busy icon briefly appears on the cursor.
I completed the same process with Notepad++ and all it's DLLs and that worked fine (using the exact same manifest file, just changing the exe)
My questions are:
Where does the UWP save files that it creates/temporary files etc? If I run an executable and it generates files next to it, where would that be when you run a UWP?
Can I set that location in the AppxManifest?
Is there anyway to see if it has run correctly or not?
Edit:
Could this be a file permissions issue? My application needs to write to 'C:\MyFolder' & creates a folder with a load of files next to the executable upon startup and that doesn't happen.
So looking into this a bit more I came across this blog which discusses preparing for conversion. I think the above file accesses probably contravene the following:
Your app writes to the install directory for your app. For example, your app writes to a log file that you put in the same directory as your exe. This isn't supported, so you'll need to find another location, like the local app data store.
This looks like a fairly halting issue, am I correct in that assumption?
If your app is writing to the install directory you will need to change that code to write to your local app data folder instead, as the preparation guide calls out.
Write operations to the install directory are not allowed in order to ensure the ability for the app deployment stack to perform seamless, differential updates and clean uninstalls of your app.
Btw, to debug through your app launch failures you can do the following in Visual Studio: Debug -> Other Debug Target -> Debug Installed App Package -> select your app from the list of installed apps.

Why does firebase warn "* You are currently outside your home directory" during an init?

I am trying to deploy my first firebase app. I am getting the message "* You are currently outside your home directory" I googled it and found this reply
"commented on Dec 6, 2016
Just to make sure you're aware. If someone is experiencing the same problem with with the command firebase init
Make the files .firebaserc and firebase.json manually and the deploy should work normally."
I do not know where to create them or what the should contain.
I have also gone to https://www.npmjs.com/package/firebase-tools to try to fix this problem.
If any one can help with this problem I would appreciate it.
If anyone else worried about this just keep going. I continued with the deployment and it deployed OK.
download firebase CLI binary (in case you didn't download it yet. this is an .exe file if you use windows).
copy the downloaded file into your project's root folder (Folder which contains all the files and folders of your projects).
run the firebase-tools-instant-win_2.exe (firebase CLI binary).
a command window will open.
execute all your command in there.
Initialize a Firebase project
Many common tasks performed using the CLI, such as deploying to a Firebase project, require a project directory. You establish a project directory using the firebase init command. A project directory is usually the same directory as your source control root, and after running firebase init, the directory contains a firebase.json configuration file.
To initialize a new Firebase project, run the following command from within your app's directory:
I used firebase init project in my project's directory to get it to work

Grunt not working in IIS application

I am running an ASP. NET application and calling a batch file using Process.Start(). The file contains some grunt commands. On opening the file using Start.Process() I get an error saying "'grunt' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n". I have added nodejs and npm to the environment variable PATH. The same code works fine on Production server.
maybe that link can help you?
https://github.com/kanema/grunt-iis

TFS The process cannot access the file because it is being used by another process

I have created an automated build process using TFS which builds a web application.
As part of this process a batch file is used to call ASP Merge to merge my web pages into one dll. I'm using the TFS activity, Invoke Process to do this.
The following is a screenshot of what is output in the TFS build window:
TFS Build Output
Does anyone have any idea how to troubleshoot this issue?
I solved this issue by removing the "Start /high /wait" command that I had in place to start the aspnet_merge tool in a separate window. The reason this was being done is because in a local script we were compiling the code files first using aspnet_compiler before running aspnet_merge.
I also had to split the rest of the file out into a different command file as it was deleting config files I needed.

Resources