I run my Shopify in local. I created a new template for a single product in the dashboard in below address:
https://yalda-dev.myshopify.com/admin/themes/125958160523?key=templates%2Fproduct.test.json
but I can't see it in VScode.
picture1: shopify code editor
picture2: vs code editor
To syncrhonize files between remote shopify and your development environment one way is to use the Shopify Cli - https://shopify.dev/themes/tools/cli
And check this guide https://shopify.dev/themes/tools/cli/getting-started#use-an-existing-theme
After you install it you run
theme get --env=yalda
And that will update all your files or
theme get --env=yalda path/to/file
to only update one file.
Related
I recently switched to VSCode from Visual Studio 2022 and needed to manage custom NuGet packages made by my company. I want it to be somewhat similar to Visual Studio 2022's NuGet Package manager.
This is what I've tried so far with no success:
NuGet Gallery VSCode extension
I downloaded the extension and installed CredentialProvider to be able to authenticate the package source
I added an environment variable with the suggested json format:
{"endpointCredentials": [{"endpoint":"http://example.index.json", "username":"optional", "password":"accesstoken"}]}
I then added the name and url as a source from the VSCode extension settings:
enter image description here
NuGet.config file in the project directory
The problem here is that it does not help me manage packages easily (browsing, updating, downgrading, etc.)
NuGet Package Manager VSCode extension
Problem here is that it has no way of configurating package registries
For information, I am using .NET 3 to 7, and the package registry is on GitLab.
Can somebody please help me fix this issue because I've looked everywhere and ran out of options?
I am new to developing for Salesforce. I have installed the Salesforce Extension Pack for Visual Studio Code. So far I have been able to create a project, authorize an org and deploy a single Apex class to a Salesforce Trailhead org.
Where I'm stuck is being able to deploy the entire package to my Salesforce org instead of just a single class. I followed the Trailhead Visual Studio Code training but it ends at deploying just a single Apex class. I've search but can't find anything that answers my question.
First you have to create Project with Manifest in Vs Code . After the update add all the class and other things to Vs code . Now update the package.xml file . You got in force-app in vs code. After then you can deploy it to org by clicking on right button .
You can right click your package file in the Explorer and select 'SFDX Deploy Source in Manifest to Org':
Alternatively, deploy from the command line with
> sfdx force:source:deploy -x path/to/package.xml
You can check docs for the CLI commands here:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_source.htm#cli_reference_force_source_deploy
I am following the azure digital twin tutorial. I am using visual studio code 1.59.0 on Mac. https://learn.microsoft.com/en-us/azure/digital-twins/tutorial-end-to-end
I like to do all from the VS code menu, skipping the azure cli.
I was able to create a function app using the deploy menu, but I can not find out how to push the .cs code to azure. All the instructions I googled have mismatching UI which does not match my own VS Code screen.
When I click on the deploy button, it only asks for the function app to push to, instead of allowing me to pick out the .cs file. When I do go thru with the push, I get a
Failed to deploy path that does not exist: /Users/xxx/workspace/digital-twins-samples/AdtSampleApp/SampleFunctionsApp/bin/Release/netcoreapp3.1/publish
I noticed some other instructions seems to indicate I must have a .zip file prepare, but that was supposed to be automatic during the deploy. So I am stuck. Can anyone help?
You can use the Kudu console to drag and drop the *.cs file to the function app as explained the article
I'm trying to deploy my first HTTP trigger Function App to Azure.
It was created with the Azure Function extension in VS Code with TypeScript template.
I use my GitRepo as a source and the Kudu build App Service.
My functions are working well locally. I can see them in VS Code > Azure tab, Local Project > Functions.
I have no error on the deployment itself but I cannot see my two functions in the Azure Functions list.
In the kudu UI, I see that all my files are correctly deployed :
Kudu screenshoot
My settings are :
settings
Where can I find some logs on what went wrong? Any idea of other things to check?
Any help will be appreciated.
I could use Zip deploy (https://learn.microsoft.com/en-us/azure/azure-functions/deployment-zip-push) as an alternative way to deploy this (I haven't tried it yet). I would like to know what's wrong with my current setup.
Not sure if the problem is that you configure the wrong runtime.
Here is the steps I did:
Create a Function app project with an http-trigger function based on TypeScript in VS Code:
Upload the project to GitHub.
Using deployment center to configure deploy from Git on portal.
After deploy, check in Functions page:
By the way, you could deploy from VS Code directly:
Suddenly I started getting an error while loading an add-in:
Error : "This add-in is no longer available: addin inserted during development are only available during debugging from visual studio. Please open your project in visual studio and re-run your application or deploy your add-in into a valid catalog and reinsert."
When I used to run the project the addin used to load automatically. Now I am getting above error.I haven't made any changes to code and word.
Note: I have installed Fiddler today but after that add-in was working. I have reset my add-in but no use.
I was not able to resolve this error. As a workaround I have created new project copied only home.html,home.js and other JS and CSS files and it works.
I also had this error recently in O365 Excel on Windows 10 but not in O365 Excel Web. In the end I solved it this way:
I ran npm run validate
This gave me a list of validation errors for the manifest.xml
I fixed the validation errors (In my case some String ids were too long)
I (re)started dev server npm stop npm start
So it seems like O365 Excel Web can cope with invalid manifest.xml to some extend whereas the app has a strikt validation of the file. I wish Office would output a meaningful error message in stead of a missleading "This add-in is no longer available". This did cost me roughly 6 hours to find out...
I had this error not for studio code but with excel but it is kind of linked
I put the staging manifest that does not contain localhost url (this was the error return during validation)
and I replace then one by one with dev config even at the end I put back localhost and it works so there is a kind of cache somewhere but I did empty the cache.
between each step I click on the drop down of Excel insert/my add in arrow and the app name under developer add in