Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 289811
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T05:56:27+00:00 2026-05-12T05:56:27+00:00

I am working on providers and cmdlets for Powershell 1 & 2. Which version(s)

  • 0

I am working on providers and cmdlets for Powershell 1 & 2.

Which version(s) of the framework should I target for my extensions?

I assume Microsoft.NET 2 will work fine. What about 3.0 and 3.5? Microsoft.NET 4.0?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T05:56:27+00:00Added an answer on May 12, 2026 at 5:56 am

    It demands 2.0, but .NET 3.0 and 3.5 still share the CLI version, so if 2.0 works, 3.0 and 3.5 should be fine if the machine has them installed; there are lots of examples of, for example, WCF (3.0) with powershell. Harder to tell on 4.0 since it isn’t RTM.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

What profilers have you used when working with .net programs, and which would you
I'm working on a few ASP.NET MVC projects which all require database functionality. Unfortunately,
I'm working on a project that will use windows role providers and I want
I've been working with providers a fair bit lately, and I came across an
I am working on a .NET internal test tool at the moment. The tool
Back again this time working with data providers. Well i been doing a bit
I'm working on a web application that uses the ASP.NET 2.0 Membership and Roles
I'm working on an application written in .NET. We are currently using ODP.NET 11's
When working with third party systems, especially very configurable systems that dynamically load providers,
Working through Jerry Lee Ford Jr.'s Powershell 2.0 for the Absolute Beginner book. There's

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.