---
title: "Why we use the properties.current.web instead of SPContext.Current.web in event receiver?"  
description: "Why we use the properties.current.web instead of SPContext.Current.web in event receiver?"  
author: "Anonymous User"  
published: 2012-09-10  
updated: 2020-09-24  
canonical: https://www.mindstick.com/interview/1535/why-we-use-the-properties-current-web-instead-of-spcontext-current-web-in-event-receiver  
category: "sharepoint"  
tags: ["sharepoint"]  
reading_time: 1 minute  

---

# Why we use the properties.current.web instead of SPContext.Current.web in event receiver?

When we deploy project from Visual studio then we can use the SPContext.Current.web but when we use the powershell to activate or deactive the feature then we have to use properties.current.web because there is no access of browser here.

## Answers

### Answer by Anonymous User

When we deploy project from Visual studio then we can use the SPContext.Current.web but when we use the powershell to activate or deactive the feature then we have to use properties.current.web because there is no access of browser here.


---

Original Source: https://www.mindstick.com/interview/1535/why-we-use-the-properties-current-web-instead-of-spcontext-current-web-in-event-receiver

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.