re: Location of the profile.msh for custom provider

Ah, that makes things much more clear.

At some point, the user will need to install your snapin. There will be an installation step. In your installation notes, you would want to make it clear that adding your formatting file to the profile is another step in the installation.

It does sound like we have the opportunity to make this experience better for snapin developers, though. If you'd like to file your ideal experience as feedback in MSConnect, it would be very helpful.

--
Lee Holmes [MSFT]
Microsoft Command Shell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.


-----Original Message-----
From: OmarVera
Posted At: Tuesday, March 21, 2006 6:31 AM
Posted To: microsoft.public.windows.server.scripting
Conversation: Location of the profile.msh for custom provider
Subject: re: Location of the profile.msh for custom provider


Hi Lee,

Thanks for your answer.
You are right, somebody can have an empty profile in the location I say. The
point that is driving me to this goal is that I am writing my own provider
and when the user executes the command >ls it shows some information that is
not useful for the user. For instance it shows a big XML and a resources
content and to filter this accessors from my objects I am using a formatting
file that is loaded from the msh profile, that is why I want to execute
always the profile; or is there another way to load a formatting XML file
without the profile?

Best Regards,

Omar Vera

"lee.holmes@xxxxxxxxxxxxxxxxxxxx" wrote:

Hi Omar;

The profile is a way for users to customize their shell environment. The side-effects are important, not the files themselves. After all, what's stopping somebody from having an empty profile at the location you require?

What is driving this goal?

If a certain side effect is important, then you should verify that instead.

--
Lee Holmes [MSFT]
Microsoft Command Shell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

-----Original Message-----
From: OmarVera
Posted At: Friday, March 17, 2006 7:22 PM
Posted To: microsoft.public.windows.server.scripting
Conversation: Location of the profile.msh for custom provider
Subject: Location of the profile.msh for custom provider


Hi all,

I am developing a provider in Monad (MSH) and I found that the default
profile file must be located either in the users dir or in the all users
documents dir. Is there a way to say the Provider to use a profile located in
the same directory where it is running? It is because I want that all users
must have the profile.msh. How can I do that?

Thanks in advance.

Omar Vera

.

Relevant Pages

  • Re: Help building MST file with Outlook 2003 and Windows XP
    ... profile and coming back to test the same account leaves registry entries, ... The Exchange server name needs to be resolvable and point to a server that is available. ... Sue Mosher, Outlook MVP ... I have created an administrative installation ...
    (microsoft.public.outlook.installation)
  • Re: Security too tight to allow certain games to run?
    ... the installation routine for this application doesn't "know" ... Start Menu folder and Desktop folder shortcuts from the user profile ... limited accounts, you can fix it to allow limited users to access the ... > If I try to install a game using Power User, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Error Message on startup
    ... Meaning I have to create a new profile? ... "PA Bear" skrev i melding ... I do, however, remember "insulting" the .NET installation ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Help building MST file with Outlook 2003 and Windows XP
    ... users Outlook profile to connect to our Exchange server using the ... The problem is the Exchange profile never does get ... I have created an administrative installation ... 18 Configure and Exchange Server Connection is selected ...
    (microsoft.public.outlook.installation)
  • Re: Network Properties screw up
    ... > You could manually copy the old profile folder to the new profile ... > the old installation had. ... I was able to reset the administrator password by ...
    (microsoft.public.win2000.networking)
Loading