We expect our system developers to all be
working within the Maker Studio environment
and then collaborating with a code
first developers code first developers.
Their environment is the IDE integrated
development environment, right?
And we want to make sure that there's
a very fluid experience going back and
forth where people who are comfortable
in their own environment don't lose
context of the business objectives of
what the apps are supposed to go do.
So to that effect,
I'm excited to kind of show you the new
VS code extension that we've now built
within VS code natively.
So here's an example,
I've got an XML file here open
within my Visual Studio environment.
I'll go select the terminal window
within Visual Studio.
Sorry I missed typing here as I speak.
If I type in PAC which stands for power,
Power, Apps,
command line or power platform,
command line and now when I type in PAC
help I can see all the different options.
The other thing I can do is with this
with this new command line tool,
I can also authenticate to various
different environments.
So in this case as an example,
when I do an auth list,
I can see that I have of authenticated
to various different environments
with different credentials as
the case may be both within admin
and user capabilities as well.
So here in this example I'm going to
do a call a command called who, who
am I in my power platform environment
and here it spits out my org ID,
the unique name of that particular
environment, the environment URL,
the friendly name. In this case it happens.
We called Toyota Dev and the user ID.
The credentials that I used along
with my S ID that I'm using to log
on to that environment.
Alright, so here's a couple of things
we're going to do.
We're now going to create a new solution,
so before we do that before
we go into new solution,
we see it's an empty directory alright,
and what I'm going to do is show
you exactly a test solution folder.
And when I'm working with the solution
in the context of a command line,
it actually looks like this, right?
It has a source code file or folder in there.
and a test solution,
CDs project file in there.
How do I create that on the command line?
So here again using pack CLI I can now
go ahead and creates a PAC solution in it.
Right, this is just like the way you
would create a solution in your web UI.
Alright,
and within that I can now specify
my publisher.
Alright, so the publisher name.
And then my publishing prefix,
within that environment,
along with the location where
I want the artifacts,
the solution artifacts will be created so
that I can go ahead and build it as it were,
right?
So I'm not specifying the publisher name.
The publisher prefix and
then I'm using the dash.
Oh, as in the output of where
the location of where I want
this particular path to show up.
Alright, I'm going to hit enter.
Alright, I made a mistake so here
apparently I only added one quote.
I forgot to quote the other one, so let me
re-type the command again.
Alright, so now I'm going to go
back all the way after right after
O put in that quote there.
And hit enter. And there you go.
So now within this solution file I now
have the CDS project file just like
the one before and I had the SRC file.
And if I go to the SRC file folder
I'll see another folder and with
other I have the customizations XML.
All the various relationships solution XML.
So as I keep adding artifacts
in this solution environment.
We start seeing more,
so let's go now I'm going to create
another VS code instance in the
context of the folder in question.
So now again here I see same
thing and now I can go ahead.
So if I'm if I'm a PCF developer now I can
add some of my PCF controls directly in
this context to be used in this solution,
which can then be diploid,
directly targeted to my
power platform environment.
But as you can see the the pack CLI can be
used for other things more than just just.
Rather than just only for PCF solution.